Web Inspector: AXI: Use loc strings for known aria-invalid types true -> "Yes" spelling -> "Spelling" grammar -> "Grammar" "false" values will be suppressed. Unknown types ("foo") and "false" will all eval to "true" and be exposed as "Yes"… If there are other types added in ARIA.Next (e.g. aria-invalid="order"), once WebKit recognizes them, we should still pass them through to the client and localize them separately. In other words, don't suppress values that WebKit knows about, even if we don't have a loc string for it yet.
> Unknown types ("foo") and "false" will all eval to "true" and be exposed as "Yes"… Typo: unknown values will be truthy, but "false" values won't.
This should be updated to use an enum for the inspector protocol, too.
Created attachment 226409 [details] patch
<rdar://problem/16286779>
Comment on attachment 226409 [details] patch cq- b/c I'll need to update the expected test result once bug 129779 lands
Comment on attachment 226409 [details] patch r=me, nice.
Created attachment 226628 [details] patch (removing minor test case updates to avoid conflicts while commit bot is down)
Comment on attachment 226628 [details] patch (removing minor test case updates to avoid conflicts while commit bot is down) Clearing flags on attachment: 226628 Committed r165597: <http://trac.webkit.org/changeset/165597>
All reviewed patches have been landed. Closing bug.