Bug 163383 - [GTK] Meters are inaccessible after r207280 - could be fixed by supporting meters in RenderThemeGtk
Summary: [GTK] Meters are inaccessible after r207280 - could be fixed by supporting me...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Accessibility (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks: 163212
  Show dependency treegraph
 
Reported: 2016-10-13 04:30 PDT by Carlos Alberto Lopez Perez
Modified: 2017-03-22 06:53 PDT (History)
5 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Comment 1 Radar WebKit Bug Importer 2016-10-13 04:30:53 PDT
<rdar://problem/28752892>
Comment 2 Carlos Alberto Lopez Perez 2016-10-13 04:44:05 PDT
Committed r207283: <http://trac.webkit.org/changeset/207283>
Comment 3 Joanmarie Diggs (irc: joanie) 2017-03-22 06:53:28 PDT
I did a bit of digging into this. Since the change in question, if the platform's RenderTheme does not support meter, HTMLMeterElement::createElementRenderer() will not create a RenderMeter. WebCore Accessibility for meters currently assumes we have a RenderMeter. So either we need to make change in how WebCore Accessibility does its thing, or RenderThemeGtk needs to start supporting meter.

Because I am completely RenderTheme ignorant, I don't know how easy doing the latter would be. But a quick test (having createElementRenderer() return a RenderMeter despite the fact that RenderThemeGtk doesn't support it) caused meters to become accessible again via ATK/AT-SPI2.