Bug 127652 - CSS bug -> h2:before { padding-right: 0.3em; }
Summary: CSS bug -> h2:before { padding-right: 0.3em; }
Status: RESOLVED WORKSFORME
Alias: None
Product: WebKit
Classification: Unclassified
Component: CSS (show other bugs)
Version: 528+ (Nightly build)
Hardware: Mac (Intel) OS X 10.7
: P2 Normal
Assignee: Nobody
URL: http://primesieve.org
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-26 10:08 PST by Kim Walisch
Modified: 2022-07-13 17:06 PDT (History)
1 user (show)

See Also:

Attachments
All <h2> are not properly aligned on first load (183.98 KB, image/jpeg)
2014-01-26 10:08 PST, Kim Walisch 		no flags Details
View All 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 Kim Walisch 2014-01-26 10:08:04 PST 
Created attachment 222276 [details]
All <h2> are not properly aligned on first load

When my website (http://primesieve.org) is loaded for the first time all <h1>, <h2>, <h3>, … are not properly aligned. Now if I hit the refresh button the bug disappears i.e. all <h1>, <h2>, <h3> are properly aligned. Below is the CSS (from http://primesieve.org/stylesheets/stylesheet_mac.css) that causes the bug:

#main-content h2 {
  font-family: 'Helvetica Neue', Helvetica, Arial, serif; 
  font-size: 22px;
  font-weight: bold;
  margin-bottom: 8px;
  color: #474747;
} 
#main-content h2:before {
  content: "//";
  color: #9ddcff;
  padding-right: 0.3em;
  margin-left: -1.33em;
}

It seems to me that 'padding-right: 0.3em;' and 'margin-left: -1.33em;' are causing the bug. The bug is not only present on my website but on all websites that use the Architect theme by Jason Long (generated by GitHub Pages).

The bug is present in both Safari and Google Chrome. The bug is not present in Firefox and Internet Explorer.
Comment 1 Brent Fulgham 2022-07-13 17:06:29 PDT 
We don't see an issue with this site at present, though it may have changed in the many years since you filed this. If you believe there is still an issue, could you please REOPEN this bug with a small test case illustrating the issue?