RESOLVED CONFIGURATION CHANGED Bug 28644
Displacement of hyperlinked elements on mouse over
https://bugs.webkit.org/show_bug.cgi?id=28644
Summary Displacement of hyperlinked elements on mouse over
jasneet
Reported 2009-08-21 17:26:00 PDT
Created attachment 38421 [details] reduced testcase Steps: Go to http://banamex.com.mx/ II Issue: Hover over footer elements and entire footer container shifts up. III Conclusion: here are 2 issues in this bug. 1) When you hover one link, all links are underlined 2) When you hover, the text moves The issue may be caused by 1) definition of a class 'boton_heder_footer' in the styles in which the <div> containing the links and the links themselves use the same class id. or 2) in the styles, they have these definitions- .boton_heder_footer:link { text-decoration:none; font-size:9px; } .boton_heder_footer:visited { text-decoration:none; font-size:9px; } .boton_heder_footer:hover { text-decoration:underline; font-size:9px; } .boton_heder_footer:active { text-decoration:none; font-size:9px; } Not sure if these were meant to have (note the a: after the class id to define the anchor tags) .boton_heder_footer a:link { text-decoration:none; font-size:9px; } .boton_heder_footer a:visited { text-decoration:none; font-size:9px; } .boton_heder_footer a:hover { text-decoration:underline; font-size:9px; } .boton_heder_footer a:active { text-decoration:none; font-size:9px; } If I set the styles to be like that of the latter, or remove the class of the <div> containing the links, then webkit behaves like that of FF and IE IV Other Browsers: IE7: ok FF3: ok V Nightly tested : 47639 Bug in Chromium : http://code.google.com/p/chromium/issues/detail?id=14606
Attachments
reduced testcase (711 bytes, text/html)
2009-08-21 17:26 PDT, jasneet
no flags
Ahmad Saleem
Comment 1 2022-08-30 05:41:56 PDT
I am able to reproduce the bug of "shifting text" and "underline whole line" in STP 152 but so does in Chrome Canary 107 and Firefox Nightly 106. It seems that all browsers agree on this behavior since it is consistent across all and Chrome also closed this bug with mentioning that it is intended CSS behavior. I am going to mark this as "RESOLVED CONFIGURATION CHANGED". But will also add few Webkit Engineers to confirm my comment. Thanks!
Note You need to log in before you can comment on or make changes to this bug.