Thank you for reporting this bug. We will make it our priority to review this report.
Is it possible to make Ext IDs more consistent?
Here's an example:
<div id="ext-gen1013" class="x-window-body x-layout-fit" ...
<div id="component-1033" ...
// Proposed change
<div id="x-gen-1013" class="x-window-body x-layout-fit" ...
<div id="x-component-1033" ...
Ext JS Premium Member
I wouldn't disable it, not that I use them for anything but debugging.
So my question to the OP is, does it really matter?
only important is that they are unique. By DOM explore you know if they are components or where they do belong, nothing more. I see no advantage to have "x-.." instead.
Release Manager of TYPO3
Consistent with what?
Component encapsulating elements are given the ID of that Component. That is very useful for debugging,
I see that the IDs are now more informative compared to Rel 3, and I like it.
>>> Consistent with what?
The format is not consistent. See the example that I pasted. In one place the ID is prefixed with "ext" and in another place, there's no prefix. The prefix "ext-gen" could be replaced by simply "x-". You can skip the "gen" part. It obvious that this is an Ext-generated ID.
I'd like to have the "x-" prefix (as in class names) for widget IDs. This is a quick visual clue that the ID was generated by Ext. I like class name format better.
The ID format in this example of these IDs is not consistent:
These are all Ext generated IDs.
Can I ask a question again? Does this matter at all?
The only requirement is that the ID is unique - we could have a random number in place of the ID and this would work.
Originally Posted by mitchellsimoens
BUT, a consistent well thought out ID format can at a glance provide more useful information.
Take a look at the Ext class names. They have a consistent format and are informative.
Ok... when do you use the IDs of the DOM elements?