NEW 54353
The update area of CSS-transformed with contenteditable does not take the focus ring into account, leading to visual artefacts 
https://bugs.webkit.org/show_bug.cgi?id=54353
Summary The update area of CSS-transformed with contenteditable does not take the foc...
Benjamin Poulain
Reported 2011-02-13 04:59:41 PST
Created attachment 82260 [details] Test case Example attached, we do not update a large enough area for the previous position. My bet is on a round() of the scaled coordinates instead of taking the biggest rect, but I'll see on debug :)
Attachments
Test case (467 bytes, text/html)
2011-02-13 04:59 PST, Benjamin Poulain 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Alexey Proskuryakov
Comment 1 2011-02-13 11:45:40 PST
Cool effect!
mitz
Comment 2 2011-02-13 11:48:31 PST
I think it’s just that the focus ring width is unaffected by the 2D transform, but the invalidation math assumes that it is.
Benjamin Poulain
Comment 3 2011-02-24 09:10:47 PST
(In reply to comment #2) > I think it’s just that the focus ring width is unaffected by the 2D transform, but the invalidation math assumes that it is. Yep, you are right. Is that the intended behavior to not transform the focus ring? It seems a bit weird. Should I look for a solution or do you have the intention to change this behavior? :)
mitz
Comment 4 2011-02-25 11:16:00 PST
(In reply to comment #3) > (In reply to comment #2) > > I think it’s just that the focus ring width is unaffected by the 2D transform, but the invalidation math assumes that it is. > > Yep, you are right. > Is that the intended behavior to not transform the focus ring? It seems a bit weird. I don’t think this was intentional. > Should I look for a solution or do you have the intention to change this behavior? :) I think a good solution would be to have the focus ring respect the transform. I am not sure how easy or even feasible this is.
Benjamin Poulain
Comment 5 2011-03-05 08:48:59 PST
Reset the assignee. I wished I would have time to fix this but I looks like I won't in the near future.
Note You need to log in before you can comment on or make changes to this bug.