Created attachment 62847 [details] Example HTML File I have found that when attributes do not have quotes, a self closing tag can cause a minor parse problem. For Example: <input type="button" type=button tabindex=1 value=Test/> <input name="title" type="text" id="title" maxLength=255 value="" tabindex=1/> The forward slash is counted as part of the last attribute. Quotes on the attribute or a space before the forward slash fixes this. I have attached an HTML file that shows this behavior. In the example, the button text shows the forward slash and the tabindexes like the above are skipped when tabbing through the fields. Note: I am not arguing whether the above HTML is valid, but it would help with compatibility with other browsers.
Thanks for the report. Believe our behavior now matches Internet Explorer, Firefox, and the HTML5 specification. For example, I loaded you example file in Firefox 3.6, Firefox 4.0b, and IE8. In all these browsers the button at the bottom right reads "Test/". Am I misunderstanding your test case? Your report asks for better compatibility with other browsers, but my understanding is that we're achieving that with this change.
Created attachment 63265 [details] Updated Example HTML File Interesting. I noticed the behavior in regards to the tabindex attribute, where Chrome & Safari *are* behaving differently from IE and Firefox. But you are right that the button example displays the same on all the browsers I tested (my mistake...bad example). Try using the tab key to go through the inputs to see the issue that I am talking about. After further testing, it seems that all the browsers I tested, including Webkit browsers, generally ignore trailing symbols at the end of most numerical attributes (tabindex, size, etc). However, Webkit browsers seems to be the only browsers that do not tolerate a symbol at the end of the tabindex attribute. I have attached an updated example showing how size=3# is accepted by all tested browsers, but tabindex=1# is only ignored by Chrome & Safari.
Created attachment 63267 [details] Updated Example HTML File (Corrected) Ooops, here is the correct updated attachment.
Does the same issue occur if you use quotes around the attribute value? It sounds like we need to loosen up our parsing of tabindex (and possibly other numerical attributes) to tolerate trailing non-digits.
*** This bug has been marked as a duplicate of bug 21076 ***