Autocompletion keymap precedence again

The way it currently works is that the keymap handler gets default precedence, and thus takes effect after high-precedence DOM handlers, or DOM handler at default precedence added before it, and before low-precedence ones or default precedence ones added after it. Is that not what you are seeing?