Bug 111241 - REGRESSION(r143614-r143830):Compose tweet button not rendering at correct height
Summary: REGRESSION(r143614-r143830):Compose tweet button not rendering at correct height
Status: VERIFIED DUPLICATE of bug 110933
Alias: None
Product: WebKit
Classification: Unclassified
Component: Layout and Rendering (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL: https://twitter.com
Keywords:
: 111070 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-03-01 20:49 PST by Chris Petersen
Modified: 2013-03-02 08:19 PST (History)
6 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Petersen 2013-03-01 20:49:51 PST
With r144510, I'm noticing the compose tweet button is not rendering at the correct height. I'm working on a final reduction of the page but I have attached a sample of the page


1) Launch Webkit NB r144510, go to https://twitter.com. Log in to your account.
2) Notice the compose tweet button is not rendered at correct height
3) I have attached a sample of page and will continue to reduce it further
Comment 1 Chris Petersen 2013-03-01 21:36:52 PST
 When CSS class is specified for inline element nested in BUTTON, the problem occurs.


<!DOCTYPE html>
  <head> 

 <style type="text/css">
.nav-tweet{height:22px}.nav-tweet{float:left;margin-top:0)
</style>
</head>
  <body>  
<button  type="button">
 <i class="nav-tweet"></i>
</button>           
</body>

</html>
Comment 2 Zan Dobersek 2013-03-01 22:34:39 PST
*** Bug 111070 has been marked as a duplicate of this bug. ***
Comment 3 Chris Petersen 2013-03-01 23:10:33 PST
Looking at the regression range. Wonder if this is the culprit - http://trac.webkit.org/changeset/143643
Comment 4 Simon Fraser (smfr) 2013-03-01 23:24:57 PST
Same as bug 110933?
Comment 5 Zan Dobersek 2013-03-02 00:25:15 PST
(In reply to comment #4)
> Same as bug 110933?

Yup.
https://bugs.webkit.org/show_bug.cgi?id=110933#c4

*** This bug has been marked as a duplicate of bug 110933 ***
Comment 6 Chris Petersen 2013-03-02 08:19:27 PST
Yes, indeed a duplicate.