Eclipse 2025-03 Next Tab navigation broken with POM XML editor.

[garretwilson]

This bug is occurring in Eclipse EE 2025-03 on Windows. (I haven't used Eclipse in over a year, so I don't know if it was introduced in an earlier version.)

Ctrl+PgUp is mapped to "Previous Tab", and Ctrl+PgDown is mapped to "Next Tab". This has been working for decades, allowing me to navigate among tabs as expected in the Eclipse IDE.

1. In Eclipse EE 2025-03, open multiple files.
2. Additionally open a Maven POM file. The POM editor shows tabs at the bottom: "Overview", "Dependencies", "Dependency Hierarchy", "Effective POM", and "pom.xml".
3. Open one more file so that its file tab shows up after the POM file tab.
4. Go back to the POM file tab and select the "pom.xml" POM view tab at the bottom. (I have this set up to the default.)
5. Select Ctrl+PgUp to go to the previous file tab.
6. The selected file is changed to the previous open file tab as expected.
7. Go back to the POM file tab.
8. Select Ctrl+PgDown to go to the next file tab.
9. Rather than going to the next open file tab, the editor switches to the previous open file tab. (Additionally, if you manually return to the POM file tab, you'll see that the editor view has changed from "pom.xml" to "Dependencies".

As you can imagine, this completely breaks navigating among file tabs when one of them is a Maven POM file. Perhaps the editor view tab hotkey mapping is overriding the global Eclipse IDE file editor tab. In any case, it is a new bug.

[iloveeclipse]

Wrong bug tracker, SDK doesn't provide POM file editors. You probably use one from m2e? Please report this issue there if this is the case: https://github.com/eclipse-m2e

[garretwilson]

Refiled as eclipse-m2e/m2e-core/issues/1970.

[castortech]

Wrong bug tracker, SDK doesn't provide POM file editors. You probably use one from m2e? Please report this issue there if this is the case: https://github.com/eclipse-m2e

I have the EXACT same issue with ecore files, starting also with 2503, is it a coincidence that m2e and emf would have the same issue?

[merks]

No probably not a coincidence. Also given I've changed nothing in EMF's editors for several releases it's not likely a change in EMF.

If you folks can pick an editor that's provided by the Platform itself, e.g., the plugin manifest editor, and demonstrate the problem there, that would make it more obvious that the issue is simply that all multi-page editors work differently than before.

Can you try that an report back? A screen capture of the state IDE to make it easier for someone else to reproduce the problem would also help...

[merks]

I'll reopen because I don't understand what these keys are doing but they don't appear to be doing something predictable or sensible to my thinking. Sometimes the tab of the multi-page editor changes, sometimes it doesn't, it behaves differently depending on whether there is an editor before and/or after the multi-page editor.

Some Ctrl-PgDn changes the active tab:

If it's the first editor the Ctrl-PgUp does nothing:

The Ctrl-PgDown still cycles but changes the active tab.

[hugithordarson]

We have the same (or similar) issue in the WOLips plugin, here's an issue, including a video demonstrating it: https://github.com/wocommunity/wolips/issues/194 .

Unfortunately I didn't catch the stack trace when the error was thrown — and it doesn't throw the error anymore (might have stopped that after I performed an in-app Eclipse update last night). Now experiencing the same unpredictable behaviour @merks describes, usually with the multi-tab editor jumping to some "subtab" of it's own, and navigation between the actual main tabs being botched.

Edit: Seeing the same behaviour in the latest integration build of 4.36

[garretwilson]

This bug is still present in Eclipse EE 2025-06, and completely borks the tab navigation.

[merks]

Given this bug is still open, I don't expect anyone has invested effort to fix it. If you look just in this repository, there are 411 issues open right now. I don't want to sound like a preacher, but there simply are not enough people to address every problem. Moreover, the people who are here contributing are more often than not paid by some organization to work on the issues that are a priority for that organization. So if this issue doesn't fall in that category it's highly likely simply to linger. The best way to avoid that is self service. We have tried to make it super easy to set up an environment to enable contribution:

https://github.com/eclipse-platform/.github/blob/main/CONTRIBUTING.md

Sorry, I don't intend any offense. We're all very busy people including you folks...

[gardellajuanpablomodusbox]

@merks thanks. From Eclipse 2025-03 and 2025-06, pom.xml source format does not work. I just checked on Error log appears:

I'm trying to find where is the correct project to submitting or open the bug, and maybe contributing. Do you know if this is the correct project? The plugin is org.eclipse.lsp4e.

[garretwilson]

@gardellajuanpablomodusbox before I took a year pause from using Eclipse, the correct place to file XML formatting problems was https://github.com/eclipse-wildwebdeveloper/wildwebdeveloper . (See for example eclipse-wildwebdeveloper/wildwebdeveloper#1251 .) I believe a few years ago they swapped out the entire XML formatting engine to something used by several platforms.

However this particular problem regarding the tabs seems to be something in the main Eclipse IDE, not with the Maven POM editor, as others in this thread have reported a similar issue with other file types.

[garretwilson]

From Eclipse 2025-03 and 2025-06, pom.xml source format does not work.

@gardellajuanpablomodusbox , I just filed eclipse-wildwebdeveloper/wildwebdeveloper#1873. Feel free to chime in on that ticket with your experience.