Bug 68506 - Bug with transition-property:margin and input pseudo classes :hover, :focus
Summary: Bug with transition-property:margin and input pseudo classes :hover, :focus
Status: RESOLVED WONTFIX
Alias: None
Product: WebKit
Classification: Unclassified
Component: CSS (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL: http://jsfiddle.net/laukstein/Gq8TE/1...
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-21 00:44 PDT by Binyamin
Modified: 2022-07-12 15:23 PDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Binyamin 2011-09-21 00:44:00 PDT 
Chrome 14, FF6, Safari 5.1, Opera 11.51 has CSS bug with transition and input:focus margin - the input element has strange juming up and down on clicking on it.
The same style input without transition is workd fine - no strange juming up and down.
Comment 1 Alexey Proskuryakov 2011-09-21 12:11:14 PDT 
This doesn't necessarily sound like a bug, but perhaps there is something that can be improved to make implementing such effects easier?
Comment 2 Binyamin 2011-09-21 22:28:16 PDT 
Alexey Proskuryakov, it is not code bug. It is definitely browser bug on CSS transition rendering. You can see it in http://jsfiddle.net/laukstein/Gq8TE/show/ .
Us much I have checked, the bug appears just for input elements (not for div's).
Comment 3 Simon Fraser (smfr) 2011-09-21 22:31:46 PDT 
Can you simplify the testcase by by setting -webkit-transition-property to something other than the default ("all")? It would be useful to know exactly which property is causing this.

Also, can it be reproduced by just transitioning outline or does focus have to be involved?
Comment 4 Binyamin 2011-09-22 04:21:47 PDT 
I have updated bug title and URL http://jsfiddle.net/laukstein/Gq8TE/1/ (editable in http://jsfiddle.net/laukstein/Gq8TE/). Like I wrote - the bug appears for property `margin`.

The same bug I posted also in http://code.google.com/p/chromium/issues/detail?id=97367
Comment 5 Brent Fulgham 2022-07-12 15:23:32 PDT 
Chrome closed as WONTFIX for similar reasons.