280585 - We don't expose <link> when made visible via CSS"

Status: NEW

(Core :: Disability Access APIs, defect)

Description

[Boris Zbarsky [:bzbarsky]]

STEPS TO REPRODUCE:

1) Load http://web.mit.edu/bzbarsky/www/index.shtml
2) Go to the View menu (in Seamonkey), and select "Use Style > Debug Look"

The page changes to an alternate stylesheet.  With this stylesheet, there are
links visible with text like "Alternate stylesheet ....."

These are <link> elements.  They're treated identically to <a> by the rendering
engine (styled like links, clicking goes to the href), but we don't expose
accessibles for them.  Note that you can also have an <img> inside a <link> in
an XML/XHTML document; this may affect how we chose to expose these.

Comment 1

[David Bolter [:davidb] (NeedInfo me for attention)]

Mass un-assigning bugs assigned to Aaron.

Comment 2

[Hubert Figuiere [:hub]]

The web page is no longer available to test.

Comment 3

[Boris Zbarsky [:bzbarsky]]

Here's the testcase:

  <style>
    :not(style) { display: block }
    link::before { content: "This is a link to mozilla.org" }
  </style>
  <link href="http://www.mozilla.org">

What does the "[bk1]" annotation mean?

Comment 4

[alexander :surkov (:asurkov)]

(In reply to Boris Zbarsky (:bz) from comment #3)
> Here's the testcase:
> 
>   <style>
>     :not(style) { display: block }
>     link::before { content: "This is a link to mozilla.org" }
>   </style>
>   <link href="http://www.mozilla.org">

Thanks, Boris.

> What does the "[bk1]" annotation mean?

I think "bugkill 1". That's annotation suggested by David to mark bugs (that were commented or closed) during a11y bug triage session so that later you can find them easily.

Comment 5

[Marco Zehe (:MarcoZ)]

Boris, do you know if this is still an issue in today's versions?

Comment 6

[Boris Zbarsky [:bzbarsky]]

I don't know, because I don't know how to get the accessible tree nowadays.  I used to do it via DOM Inspector, but in today's build that's telling me that <a href="http://example.com">hey</a> doesn't have an accessible, which sounds dubious.

For someone who knows how to get an accessible tree, just load the testcase in comment 3 and see what the accessible tree looks like...