[Webkit-unassigned] [Bug 95644] [Gtk] accessibility/canvas-description-and-role expected results needed

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Sep 4 11:43:22 PDT 2012


--- Comment #8 from Dominic Mazzoni <dmazzoni at google.com>  2012-09-04 11:43:35 PST ---
(In reply to comment #7)
> And I do see your point. But in that case it's not really a platform thing, is it? In other words, case 1 is a static image for all users of all platforms. Thus perhaps in that instance, WebCore a11y should determine that it is ImageRole rather than CanvasRole and only declare CanvasRole for those objects which are functionally canvas.

I don't have strong feelings either way, but you could argue that approach would "lose information" - if a platform didn't want a static canvas to be an ImageRole, it wouldn't have a way to do that.

I just felt it was the most clear for WebCore to always call a canvas a canvas - but provide platforms with enough information to distinguish between static and dynamic canvases *if they want*.

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list