[wp-trac] [WordPress Trac] #60680: Site's broken

[WordPress Trac]

#60680: Site's broken
--------------------------------+------------------------------
 Reporter:  rsalafy             |       Owner:  (none)
     Type:  defect (bug)        |      Status:  new
 Priority:  normal              |   Milestone:  Awaiting Review
Component:  WordPress.org Site  |     Version:
 Severity:  critical            |  Resolution:
 Keywords:                      |     Focuses:
--------------------------------+------------------------------

Comment (by sabernhardt):

 The video "output.mp4" shows a visit to
 https://developer.wordpress.org/apis/wp-config-php/#moving-plugin-folder

 As page loads:
 - The viewport is wide.
 - The header contains the WordPress global header and the WordPress
 Developer Resources header.
 - Under the Search Resources search form, there is a large empty space.
 - The heading and first paragraph are not visible yet.
 - The Chapters list and the "In this article" box both appear on the right
 half of the screen.

 Scrolling down:
 - The global header disappears, but the WordPress Developer Resources
 header is fixed at the top. The W logo drops down (or stays) in the top
 left corner. The "wp-config.php" page heading moved into the fixed header
 next to "WordPress Developer Resources."
 - The first few paragraphs appear, positioned from the left edge of the
 page content area.
 - The Chapters list is also positioned on the left side, in front of the
 article information.
 - The "In this article" box remains fixed on the right side, and the
 article content does not extend that far (the article text covers about
 three fourths and then the side navigation is about one-fourth).

 In my experience, the page has three columns as it loads: a Chapters list,
 the article content, and the "In this article" box. The columns remain
 that way when scrolling down, and the left and right side columns stay
 fixed in place.

 I was able to achieve a different type of overlap in Chrome by scrolling
 down, disabling JavaScript without refreshing, and scrolling back up.
 However, a script failure likely was not the cause (at least not on its
 own) since the article content was in the middle. For another possibility,
 I think that the `.is-layout-*` classes might have failed to work properly
 at that time.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/60680#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform