Bug 110965
| Summary: | Allow focus ring quads to be computed relative to container | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Arvid Nilsson <anilsson> |
| Component: | Layout and Rendering | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | anilsson, jpetsovits, mifenton, simon.fraser, tonikitoo, wangxianzhu |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Arvid Nilsson
Currently, it's possible to compute the absolute focus ring quads, but with a minor tweak it would be possible to compute them relative to container as well.
The BlackBerry port has always rendered the focus ring ("tap highlight", we call it) as a separate overlay to avoid re-rendering the page when the user taps a link. This is an optimisation. We're now switching to an approach where the tap highlight overlay is a child of the container that contains the tapped element. This allows our tap highlight overlay to move along with scrollable divs, frames, fixed pos items etc despite being a separate overlay. Unfortunately, the tap highlight computations currently do not support transforms, and this patch will not change that.
I want to put the patch up for review here to get your feedback.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Arvid Nilsson
BlackBerry PR #186234
Simon Fraser (smfr)
See also bug 110895