• Welcome to Tux Reports: Where Penguins Fly. We hope you find the topics varied, interesting, and worthy of your time. Please become a member and join in the discussions.

bug in ie8's querySelectorAll implementation

M

miketaylr

Flightless Bird
Hello, I'm not sure exactly where to submit a bug report--I couldn't find
anywhere on the IE Feedback page
(https://connect.microsoft.com/IE/Feedback?wa=wsignin1.0). If this is the
wrong place, please forgive me (and point me in the right direction!)

According to the W3C spec, document.querySelectorAll('[selected=selected]')
should return the same NodeList as document.querySelectorAll('[selected]'),
however this is currently not the case.
document.querySelectorAll('[selected]') fails in all cases that I've tested.

Here is a simplified test case: http://miketaylr.com/test/ie8qsa.html, with
just one <select> element that contains an <option selected=selected>
element, with a few more plain <options>.

Furthermore, from the spec, "If the user agent also supports some level of
CSS, the implementation should support the same set of selectors in both
these APIs and CSS."

IE8 clearly supports the [attr] {} selector syntax, as can be seen in the
test case, with the [multiple] {font-weight:bold} style.

This is a major bug, especially for JavaScript libraries such as jQuery,
Dojo, and Prototype that rely on IE8's QSA implementation for their selector
engines.

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/communitie...&dg=microsoft.public.internetexplorer.general
 
R

rob^_^

Flightless Bird
Hi Mike,

at https://connect.microsoft.com/IE/Feedback

You have to do a Search first before the "Submit Feedback" will appear on
the bottom lhs of the page.

I don't know if this is "by design" but it sure as heck confuses ppl.

Regards.

"miketaylr" <miketaylr@discussions.microsoft.com> wrote in message
news:B337AE1E-8041-473A-BA94-F23BEE4CD506@microsoft.com...
> Hello, I'm not sure exactly where to submit a bug report--I couldn't find
> anywhere on the IE Feedback page
> (https://connect.microsoft.com/IE/Feedback?wa=wsignin1.0). If this is the
> wrong place, please forgive me (and point me in the right direction!)
>
> According to the W3C spec,
> document.querySelectorAll('[selected=selected]')
> should return the same NodeList as
> document.querySelectorAll('[selected]'),
> however this is currently not the case.
> document.querySelectorAll('[selected]') fails in all cases that I've
> tested.
>
> Here is a simplified test case: http://miketaylr.com/test/ie8qsa.html,
> with
> just one <select> element that contains an <option selected=selected>
> element, with a few more plain <options>.
>
> Furthermore, from the spec, "If the user agent also supports some level of
> CSS, the implementation should support the same set of selectors in both
> these APIs and CSS."
>
> IE8 clearly supports the [attr] {} selector syntax, as can be seen in the
> test case, with the [multiple] {font-weight:bold} style.
>
> This is a major bug, especially for JavaScript libraries such as jQuery,
> Dojo, and Prototype that rely on IE8's QSA implementation for their
> selector
> engines.
>
> ----------------
> This post is a suggestion for Microsoft, and Microsoft responds to the
> suggestions with the most votes. To vote for this suggestion, click the "I
> Agree" button in the message pane. If you do not see the button, follow
> this
> link to open the suggestion in the Microsoft Web-based Newsreader and then
> click "I Agree" in the message pane.
>
> http://www.microsoft.com/communitie...&dg=microsoft.public.internetexplorer.general
>
 
M

miketaylr

Flightless Bird
"rob^_^" wrote:

> Hi Mike,
>
> at https://connect.microsoft.com/IE/Feedback
>
> You have to do a Search first before the "Submit Feedback" will appear on
> the bottom lhs of the page.
>
> I don't know if this is "by design" but it sure as heck confuses ppl.
>
> Regards.

Thanks for the response, rob.

Unfortunately, even after the search I don't get a "Submit Feedback" button,
in any browser. Here's a screenshot for posterity:
http://miketaylr.com/post/ca7dc860.png

This begs the question, where does one report bugs for the bug tracker? I
suppose I'll just have to wait for some benevolent IE dev to find this and
file a proper issue.


>
> "miketaylr" <miketaylr@discussions.microsoft.com> wrote in message
> news:B337AE1E-8041-473A-BA94-F23BEE4CD506@microsoft.com...
> > Hello, I'm not sure exactly where to submit a bug report--I couldn't find
> > anywhere on the IE Feedback page
> > (https://connect.microsoft.com/IE/Feedback?wa=wsignin1.0). If this is the
> > wrong place, please forgive me (and point me in the right direction!)
> >
> > According to the W3C spec,
> > document.querySelectorAll('[selected=selected]')
> > should return the same NodeList as
> > document.querySelectorAll('[selected]'),
> > however this is currently not the case.
> > document.querySelectorAll('[selected]') fails in all cases that I've
> > tested.
> >
> > Here is a simplified test case: http://miketaylr.com/test/ie8qsa.html,
> > with
> > just one <select> element that contains an <option selected=selected>
> > element, with a few more plain <options>.
> >
> > Furthermore, from the spec, "If the user agent also supports some level of
> > CSS, the implementation should support the same set of selectors in both
> > these APIs and CSS."
> >
> > IE8 clearly supports the [attr] {} selector syntax, as can be seen in the
> > test case, with the [multiple] {font-weight:bold} style.
> >
> > This is a major bug, especially for JavaScript libraries such as jQuery,
> > Dojo, and Prototype that rely on IE8's QSA implementation for their
> > selector
> > engines.
> >
> > ----------------
> > This post is a suggestion for Microsoft, and Microsoft responds to the
> > suggestions with the most votes. To vote for this suggestion, click the "I
> > Agree" button in the message pane. If you do not see the button, follow
> > this
> > link to open the suggestion in the Microsoft Web-based Newsreader and then
> > click "I Agree" in the message pane.
> >
> > http://www.microsoft.com/communitie...&dg=microsoft.public.internetexplorer.general
> >
 
R

rob^_^

Flightless Bird
Hi Mike,

From your screen shot, it looks like you are not logged in. Have you joined
up and added IE to your dashboard there?

You need to do this first in order to have access to submit issue tickets
(otherwise the connect team will not be able to inform your of the tickets
progress through the triage and resolution process. Its been a long time
since I joined so I am not sure if the "Membership" process has changed (I
think you still need either a passport or Live mail account).

Post back if you cannot join up and I can post it for you (or someone else
here who has access).

I had a cursory look at your test case but have not tried pulling it apart
to determine whether your HTML 5 DTD has a bearing on the expected outcome.
You can see that IE8 defaults with the IE8 Standards mode (HTML 4, CSS 2.1
etc )

I think we also need to check with the IE Test suite (link not at hand) to
see if there is an existing Unit Test that already documents any
shortcomings in standards compliance or its implementation in IE8. If there
is we can refer to it in the issue submission to escalate its importance.

One thing I did notice in your Test case running in the other browsers was
the lack of a pointer cursor over the selection list. Both FX and Chrome
display an IBeam cursor, making it difficult to select items in the list.
But yes the results differ from those in IE8.

Post back if you can't join up and I can spend some time making a post
(credited to you) on your behalf.

Regards.



"miketaylr" <miketaylr@discussions.microsoft.com> wrote in message
news:280F65A1-C9C5-4126-81D0-C7AC78B05F02@microsoft.com...
>
>
> "rob^_^" wrote:
>
>> Hi Mike,
>>
>> at https://connect.microsoft.com/IE/Feedback
>>
>> You have to do a Search first before the "Submit Feedback" will appear on
>> the bottom lhs of the page.
>>
>> I don't know if this is "by design" but it sure as heck confuses ppl.
>>
>> Regards.
>
> Thanks for the response, rob.
>
> Unfortunately, even after the search I don't get a "Submit Feedback"
> button,
> in any browser. Here's a screenshot for posterity:
> http://miketaylr.com/post/ca7dc860.png
>
> This begs the question, where does one report bugs for the bug tracker? I
> suppose I'll just have to wait for some benevolent IE dev to find this and
> file a proper issue.
>
>
>>
>> "miketaylr" <miketaylr@discussions.microsoft.com> wrote in message
>> news:B337AE1E-8041-473A-BA94-F23BEE4CD506@microsoft.com...
>> > Hello, I'm not sure exactly where to submit a bug report--I couldn't
>> > find
>> > anywhere on the IE Feedback page
>> > (https://connect.microsoft.com/IE/Feedback?wa=wsignin1.0). If this is
>> > the
>> > wrong place, please forgive me (and point me in the right direction!)
>> >
>> > According to the W3C spec,
>> > document.querySelectorAll('[selected=selected]')
>> > should return the same NodeList as
>> > document.querySelectorAll('[selected]'),
>> > however this is currently not the case.
>> > document.querySelectorAll('[selected]') fails in all cases that I've
>> > tested.
>> >
>> > Here is a simplified test case: http://miketaylr.com/test/ie8qsa.html,
>> > with
>> > just one <select> element that contains an <option selected=selected>
>> > element, with a few more plain <options>.
>> >
>> > Furthermore, from the spec, "If the user agent also supports some level
>> > of
>> > CSS, the implementation should support the same set of selectors in
>> > both
>> > these APIs and CSS."
>> >
>> > IE8 clearly supports the [attr] {} selector syntax, as can be seen in
>> > the
>> > test case, with the [multiple] {font-weight:bold} style.
>> >
>> > This is a major bug, especially for JavaScript libraries such as
>> > jQuery,
>> > Dojo, and Prototype that rely on IE8's QSA implementation for their
>> > selector
>> > engines.
>> >
>> > ----------------
>> > This post is a suggestion for Microsoft, and Microsoft responds to the
>> > suggestions with the most votes. To vote for this suggestion, click the
>> > "I
>> > Agree" button in the message pane. If you do not see the button, follow
>> > this
>> > link to open the suggestion in the Microsoft Web-based Newsreader and
>> > then
>> > click "I Agree" in the message pane.
>> >
>> > http://www.microsoft.com/communitie...&dg=microsoft.public.internetexplorer.general
>> >
 
R

rob^_^

Flightless Bird
Hi Mike,

Please remove the Google urchin code from your test page.

Sish... what's the go?

Lucky I had my InPrivate filtering on.. he he.. you didn't catch me.

I don't think I should say regards...
<plonk>

"miketaylr" <miketaylr@discussions.microsoft.com> wrote in message
news:B337AE1E-8041-473A-BA94-F23BEE4CD506@microsoft.com...
> Hello, I'm not sure exactly where to submit a bug report--I couldn't find
> anywhere on the IE Feedback page
> (https://connect.microsoft.com/IE/Feedback?wa=wsignin1.0). If this is the
> wrong place, please forgive me (and point me in the right direction!)
>
> According to the W3C spec,
> document.querySelectorAll('[selected=selected]')
> should return the same NodeList as
> document.querySelectorAll('[selected]'),
> however this is currently not the case.
> document.querySelectorAll('[selected]') fails in all cases that I've
> tested.
>
> Here is a simplified test case: http://miketaylr.com/test/ie8qsa.html,
> with
> just one <select> element that contains an <option selected=selected>
> element, with a few more plain <options>.
>
> Furthermore, from the spec, "If the user agent also supports some level of
> CSS, the implementation should support the same set of selectors in both
> these APIs and CSS."
>
> IE8 clearly supports the [attr] {} selector syntax, as can be seen in the
> test case, with the [multiple] {font-weight:bold} style.
>
> This is a major bug, especially for JavaScript libraries such as jQuery,
> Dojo, and Prototype that rely on IE8's QSA implementation for their
> selector
> engines.
>
> ----------------
> This post is a suggestion for Microsoft, and Microsoft responds to the
> suggestions with the most votes. To vote for this suggestion, click the "I
> Agree" button in the message pane. If you do not see the button, follow
> this
> link to open the suggestion in the Microsoft Web-based Newsreader and then
> click "I Agree" in the message pane.
>
> http://www.microsoft.com/communitie...&dg=microsoft.public.internetexplorer.general
>
 
M

miketaylr

Flightless Bird
"rob^_^" wrote:

> Hi Mike,
>
> Please remove the Google urchin code from your test page.
>
> Sish... what's the go?

Eh, that's in there in a default template. And certainly not affecting the
test case.

>
> Lucky I had my InPrivate filtering on.. he he.. you didn't catch me.
>
> I don't think I should say regards...
> <plonk>

Wow, really?

>
> "miketaylr" <miketaylr@discussions.microsoft.com> wrote in message
> news:B337AE1E-8041-473A-BA94-F23BEE4CD506@microsoft.com...
> > Hello, I'm not sure exactly where to submit a bug report--I couldn't find
> > anywhere on the IE Feedback page
> > (https://connect.microsoft.com/IE/Feedback?wa=wsignin1.0). If this is the
> > wrong place, please forgive me (and point me in the right direction!)
> >
> > According to the W3C spec,
> > document.querySelectorAll('[selected=selected]')
> > should return the same NodeList as
> > document.querySelectorAll('[selected]'),
> > however this is currently not the case.
> > document.querySelectorAll('[selected]') fails in all cases that I've
> > tested.
> >
> > Here is a simplified test case: http://miketaylr.com/test/ie8qsa.html,
> > with
> > just one <select> element that contains an <option selected=selected>
> > element, with a few more plain <options>.
> >
> > Furthermore, from the spec, "If the user agent also supports some level of
> > CSS, the implementation should support the same set of selectors in both
> > these APIs and CSS."
> >
> > IE8 clearly supports the [attr] {} selector syntax, as can be seen in the
> > test case, with the [multiple] {font-weight:bold} style.
> >
> > This is a major bug, especially for JavaScript libraries such as jQuery,
> > Dojo, and Prototype that rely on IE8's QSA implementation for their
> > selector
> > engines.
> >
> > ----------------
> > This post is a suggestion for Microsoft, and Microsoft responds to the
> > suggestions with the most votes. To vote for this suggestion, click the "I
> > Agree" button in the message pane. If you do not see the button, follow
> > this
> > link to open the suggestion in the Microsoft Web-based Newsreader and then
> > click "I Agree" in the message pane.
> >
> > http://www.microsoft.com/communitie...&dg=microsoft.public.internetexplorer.general
> >
 
M

miketaylr

Flightless Bird
"rob^_^" wrote:

> Hi Mike,
>
> From your screen shot, it looks like you are not logged in. Have you joined
> up and added IE to your dashboard there?

I actually was logged in--that part was cut off in the screenshot. Here's
another that shows me logged in, with Internet Explorer added to my
dashboard.
http://miketaylr.com/post/d2757359.png

>
> You need to do this first in order to have access to submit issue tickets
> (otherwise the connect team will not be able to inform your of the tickets
> progress through the triage and resolution process. Its been a long time
> since I joined so I am not sure if the "Membership" process has changed (I
> think you still need either a passport or Live mail account).
>
> Post back if you cannot join up and I can post it for you (or someone else
> here who has access).


>
> I had a cursory look at your test case but have not tried pulling it apart
> to determine whether your HTML 5 DTD has a bearing on the expected outcome.

HTML 5 doesn't have a DTD, but the doctype will render pages in standards
mode. Cf. http://hsivonen.iki.fi/doctype/

> You can see that IE8 defaults with the IE8 Standards mode (HTML 4, CSS 2.1
> etc )
>
> I think we also need to check with the IE Test suite (link not at hand) to
> see if there is an existing Unit Test that already documents any
> shortcomings in standards compliance or its implementation in IE8. If there
> is we can refer to it in the issue submission to escalate its importance.
>
> One thing I did notice in your Test case running in the other browsers was
> the lack of a pointer cursor over the selection list. Both FX and Chrome
> display an IBeam cursor, making it difficult to select items in the list.
> But yes the results differ from those in IE8.

It's true, but I'm not doing anything with cursor here.

>
> Post back if you can't join up and I can spend some time making a post
> (credited to you) on your behalf.
>

Thank you, I'd appreciate it.

> Regards.
>
>
>
> "miketaylr" <miketaylr@discussions.microsoft.com> wrote in message
> news:280F65A1-C9C5-4126-81D0-C7AC78B05F02@microsoft.com...
> >
> >
> > "rob^_^" wrote:
> >
> >> Hi Mike,
> >>
> >> at https://connect.microsoft.com/IE/Feedback
> >>
> >> You have to do a Search first before the "Submit Feedback" will appear on
> >> the bottom lhs of the page.
> >>
> >> I don't know if this is "by design" but it sure as heck confuses ppl.
> >>
> >> Regards.
> >
> > Thanks for the response, rob.
> >
> > Unfortunately, even after the search I don't get a "Submit Feedback"
> > button,
> > in any browser. Here's a screenshot for posterity:
> > http://miketaylr.com/post/ca7dc860.png
> >
> > This begs the question, where does one report bugs for the bug tracker? I
> > suppose I'll just have to wait for some benevolent IE dev to find this and
> > file a proper issue.
> >
> >
> >>
> >> "miketaylr" <miketaylr@discussions.microsoft.com> wrote in message
> >> news:B337AE1E-8041-473A-BA94-F23BEE4CD506@microsoft.com...
> >> > Hello, I'm not sure exactly where to submit a bug report--I couldn't
> >> > find
> >> > anywhere on the IE Feedback page
> >> > (https://connect.microsoft.com/IE/Feedback?wa=wsignin1.0). If this is
> >> > the
> >> > wrong place, please forgive me (and point me in the right direction!)
> >> >
> >> > According to the W3C spec,
> >> > document.querySelectorAll('[selected=selected]')
> >> > should return the same NodeList as
> >> > document.querySelectorAll('[selected]'),
> >> > however this is currently not the case.
> >> > document.querySelectorAll('[selected]') fails in all cases that I've
> >> > tested.
> >> >
> >> > Here is a simplified test case: http://miketaylr.com/test/ie8qsa.html,
> >> > with
> >> > just one <select> element that contains an <option selected=selected>
> >> > element, with a few more plain <options>.
> >> >
> >> > Furthermore, from the spec, "If the user agent also supports some level
> >> > of
> >> > CSS, the implementation should support the same set of selectors in
> >> > both
> >> > these APIs and CSS."
> >> >
> >> > IE8 clearly supports the [attr] {} selector syntax, as can be seen in
> >> > the
> >> > test case, with the [multiple] {font-weight:bold} style.
> >> >
> >> > This is a major bug, especially for JavaScript libraries such as
> >> > jQuery,
> >> > Dojo, and Prototype that rely on IE8's QSA implementation for their
> >> > selector
> >> > engines.
> >> >
> >> > ----------------
> >> > This post is a suggestion for Microsoft, and Microsoft responds to the
> >> > suggestions with the most votes. To vote for this suggestion, click the
> >> > "I
> >> > Agree" button in the message pane. If you do not see the button, follow
> >> > this
> >> > link to open the suggestion in the Microsoft Web-based Newsreader and
> >> > then
> >> > click "I Agree" in the message pane.
> >> >
> >> > http://www.microsoft.com/communitie...&dg=microsoft.public.internetexplorer.general
> >> >
 
R

rob^_^

Flightless Bird
Hi,

If it was placed there by accident then please remove it. If you wish to
track visitation to your test page can't you use your server logs?

Its important your test cases are exactly that... no external code...
sandboxed... to rule out anything but the issue you are testing.

Regards.

I forgive you... but please no external code. especially g's urchin

"miketaylr" <miketaylr@discussions.microsoft.com> wrote in message
news:ADD4E7A6-C75F-4EF5-B804-A8510DF35A12@microsoft.com...
>
>
> "rob^_^" wrote:
>
>> Hi Mike,
>>
>> Please remove the Google urchin code from your test page.
>>
>> Sish... what's the go?
>
> Eh, that's in there in a default template. And certainly not affecting the
> test case.
>
>>
>> Lucky I had my InPrivate filtering on.. he he.. you didn't catch me.
>>
>> I don't think I should say regards...
>> <plonk>
>
> Wow, really?
>
>>
>> "miketaylr" <miketaylr@discussions.microsoft.com> wrote in message
>> news:B337AE1E-8041-473A-BA94-F23BEE4CD506@microsoft.com...
>> > Hello, I'm not sure exactly where to submit a bug report--I couldn't
>> > find
>> > anywhere on the IE Feedback page
>> > (https://connect.microsoft.com/IE/Feedback?wa=wsignin1.0). If this is
>> > the
>> > wrong place, please forgive me (and point me in the right direction!)
>> >
>> > According to the W3C spec,
>> > document.querySelectorAll('[selected=selected]')
>> > should return the same NodeList as
>> > document.querySelectorAll('[selected]'),
>> > however this is currently not the case.
>> > document.querySelectorAll('[selected]') fails in all cases that I've
>> > tested.
>> >
>> > Here is a simplified test case: http://miketaylr.com/test/ie8qsa.html,
>> > with
>> > just one <select> element that contains an <option selected=selected>
>> > element, with a few more plain <options>.
>> >
>> > Furthermore, from the spec, "If the user agent also supports some level
>> > of
>> > CSS, the implementation should support the same set of selectors in
>> > both
>> > these APIs and CSS."
>> >
>> > IE8 clearly supports the [attr] {} selector syntax, as can be seen in
>> > the
>> > test case, with the [multiple] {font-weight:bold} style.
>> >
>> > This is a major bug, especially for JavaScript libraries such as
>> > jQuery,
>> > Dojo, and Prototype that rely on IE8's QSA implementation for their
>> > selector
>> > engines.
>> >
>> > ----------------
>> > This post is a suggestion for Microsoft, and Microsoft responds to the
>> > suggestions with the most votes. To vote for this suggestion, click the
>> > "I
>> > Agree" button in the message pane. If you do not see the button, follow
>> > this
>> > link to open the suggestion in the Microsoft Web-based Newsreader and
>> > then
>> > click "I Agree" in the message pane.
>> >
>> > http://www.microsoft.com/communitie...&dg=microsoft.public.internetexplorer.general
>> >
 
R

rob^_^

Flightless Bird
Hi,

Sorry,

From IE8 Feedback Home

select the "Feedback" menu link on the lhs.

Then do your search.

The search results page with have the "Submit Feedback" button on the bottom
lhs.

Regards.

"miketaylr" <miketaylr@discussions.microsoft.com> wrote in message
news:95996B8A-9A2F-436C-8637-304844B04626@microsoft.com...
>
>
> "rob^_^" wrote:
>
>> Hi Mike,
>>
>> From your screen shot, it looks like you are not logged in. Have you
>> joined
>> up and added IE to your dashboard there?
>
> I actually was logged in--that part was cut off in the screenshot. Here's
> another that shows me logged in, with Internet Explorer added to my
> dashboard.
> http://miketaylr.com/post/d2757359.png
>
>>
>> You need to do this first in order to have access to submit issue tickets
>> (otherwise the connect team will not be able to inform your of the
>> tickets
>> progress through the triage and resolution process. Its been a long time
>> since I joined so I am not sure if the "Membership" process has changed
>> (I
>> think you still need either a passport or Live mail account).
>>
>> Post back if you cannot join up and I can post it for you (or someone
>> else
>> here who has access).
>
>
>>
>> I had a cursory look at your test case but have not tried pulling it
>> apart
>> to determine whether your HTML 5 DTD has a bearing on the expected
>> outcome.
>
> HTML 5 doesn't have a DTD, but the doctype will render pages in standards
> mode. Cf. http://hsivonen.iki.fi/doctype/
>
>> You can see that IE8 defaults with the IE8 Standards mode (HTML 4, CSS
>> 2.1
>> etc )
>>
>> I think we also need to check with the IE Test suite (link not at hand)
>> to
>> see if there is an existing Unit Test that already documents any
>> shortcomings in standards compliance or its implementation in IE8. If
>> there
>> is we can refer to it in the issue submission to escalate its importance.
>>
>> One thing I did notice in your Test case running in the other browsers
>> was
>> the lack of a pointer cursor over the selection list. Both FX and Chrome
>> display an IBeam cursor, making it difficult to select items in the list.
>> But yes the results differ from those in IE8.
>
> It's true, but I'm not doing anything with cursor here.
>
>>
>> Post back if you can't join up and I can spend some time making a post
>> (credited to you) on your behalf.
>>
>
> Thank you, I'd appreciate it.
>
>> Regards.
>>
>>
>>
>> "miketaylr" <miketaylr@discussions.microsoft.com> wrote in message
>> news:280F65A1-C9C5-4126-81D0-C7AC78B05F02@microsoft.com...
>> >
>> >
>> > "rob^_^" wrote:
>> >
>> >> Hi Mike,
>> >>
>> >> at https://connect.microsoft.com/IE/Feedback
>> >>
>> >> You have to do a Search first before the "Submit Feedback" will appear
>> >> on
>> >> the bottom lhs of the page.
>> >>
>> >> I don't know if this is "by design" but it sure as heck confuses ppl.
>> >>
>> >> Regards.
>> >
>> > Thanks for the response, rob.
>> >
>> > Unfortunately, even after the search I don't get a "Submit Feedback"
>> > button,
>> > in any browser. Here's a screenshot for posterity:
>> > http://miketaylr.com/post/ca7dc860.png
>> >
>> > This begs the question, where does one report bugs for the bug tracker?
>> > I
>> > suppose I'll just have to wait for some benevolent IE dev to find this
>> > and
>> > file a proper issue.
>> >
>> >
>> >>
>> >> "miketaylr" <miketaylr@discussions.microsoft.com> wrote in message
>> >> news:B337AE1E-8041-473A-BA94-F23BEE4CD506@microsoft.com...
>> >> > Hello, I'm not sure exactly where to submit a bug report--I couldn't
>> >> > find
>> >> > anywhere on the IE Feedback page
>> >> > (https://connect.microsoft.com/IE/Feedback?wa=wsignin1.0). If this
>> >> > is
>> >> > the
>> >> > wrong place, please forgive me (and point me in the right
>> >> > direction!)
>> >> >
>> >> > According to the W3C spec,
>> >> > document.querySelectorAll('[selected=selected]')
>> >> > should return the same NodeList as
>> >> > document.querySelectorAll('[selected]'),
>> >> > however this is currently not the case.
>> >> > document.querySelectorAll('[selected]') fails in all cases that I've
>> >> > tested.
>> >> >
>> >> > Here is a simplified test case:
>> >> > http://miketaylr.com/test/ie8qsa.html,
>> >> > with
>> >> > just one <select> element that contains an <option
>> >> > selected=selected>
>> >> > element, with a few more plain <options>.
>> >> >
>> >> > Furthermore, from the spec, "If the user agent also supports some
>> >> > level
>> >> > of
>> >> > CSS, the implementation should support the same set of selectors in
>> >> > both
>> >> > these APIs and CSS."
>> >> >
>> >> > IE8 clearly supports the [attr] {} selector syntax, as can be seen
>> >> > in
>> >> > the
>> >> > test case, with the [multiple] {font-weight:bold} style.
>> >> >
>> >> > This is a major bug, especially for JavaScript libraries such as
>> >> > jQuery,
>> >> > Dojo, and Prototype that rely on IE8's QSA implementation for their
>> >> > selector
>> >> > engines.
>> >> >
>> >> > ----------------
>> >> > This post is a suggestion for Microsoft, and Microsoft responds to
>> >> > the
>> >> > suggestions with the most votes. To vote for this suggestion, click
>> >> > the
>> >> > "I
>> >> > Agree" button in the message pane. If you do not see the button,
>> >> > follow
>> >> > this
>> >> > link to open the suggestion in the Microsoft Web-based Newsreader
>> >> > and
>> >> > then
>> >> > click "I Agree" in the message pane.
>> >> >
>> >> > http://www.microsoft.com/communitie...&dg=microsoft.public.internetexplorer.general
>> >> >
 
You must log in or register to reply here.
Top