So navigation keys not doing actual navigation is more intuitive? That seems odd, especially now when you hit down once the key is now redundant and has no functionality.

On top of that, you also have two keys doing exactly the same thing in the current setup, HOME and up do the same thing and the functionality of going to previous and next now requires three key presses in each case.
So based on that i'd also claim the current system wastes the up and down keys.
this is XY, not DO, so there will be some differences..
Yes, but in this regard DO is doing a
far better job hence why I suggested it's a feature that would be extremely useful.
It seems like my only option is to convert back to Directory Opus for file editing then? Filename editing is a core feature of a filemanager afterall. Or use a third party app to override default behaviour?
I would greatly appreciate having the ability to either remap the less intuitive functionality and put on a quick edit functionality. Or if you release the source i could always patch it myself hehe..
And maybe have Ctrl+Enter, or Ctrl+Up/Down, or PageUp/PageDown to do what you want :
I'd hate that because your having to reach all over the keyboard to achieving something that is performed much more regularly than the current use of up and down. Its the current up+down functionality that is the rarity surely, not the editing multiple filenames. At least i'd be utterly amazed if it wasn't.
Same goes for 'scripting' a chain of keys, they usually don't respond fast at all but i'd be interested to see.
Sounds like the best solution that will annoy the least set is simply to have a "quick filename navigation" checkbox in options, or a keyremapper option with the ability to map down to go to next item in edit mode. It doesn't have to be in quick edit mode by default
Why would then Right/Left not validate and move to the file on the right/left? Because it's sounds awfully illogic?
Try it in Directory Opus, its previous (up) and next (down), and left (before) and right (after). They also have the same excluding of filename. Works brilliantly. I assume that's why they implemented it like that. Put 50 files bung them in a directory and rename them all, with a non-standard pattern. A couple of them sequentially, a couple of them completely, the rest just minor tweaks/removals/additions. See how long it takes with the current system. Edit, enter, down, f2, edit, copy, enter, down f2... takes ages for something that takes a much shorter time in DO. Now imagine having to hit ctrl+enter, your going to end up with carpel tunnel. While i'm growing to prefer XY in a lot of areas, this is one where its proving substantially weaker/slower. Batch proves decent enough for a set renaming patern.
I ask you to play with DO system and see what you think, it really is better for mass edits.
Less intuitive to you perhaps, but maybe not to those coming from Win Expl...
Maybe is certainly the word to use, and for people coming from explorer such a change will be the least of their confusion

Explorer's implementation of things is bad remember, that's why we've all opted to replace it; keeping a bad editing system for the sake of sticking close to explorer isn't a good thing imo.
keeping something like Explorer for the sake of it is a terrible idea imo.