Page MenuHomePhabricator

Schema code samples popup appears under the JSON table
Open, Needs TriagePublic

Assigned To
None
Authored By
He7d3r
Jan 25 2021, 2:45 PM
Referenced Files
F36914394: Screenshot 2023-03-16 at 13.47.35.png
Mar 16 2023, 1:57 PM
Restricted File
Mar 16 2023, 1:56 PM
F36914387: Screenshot 2023-03-16 at 13.45.56.png
Mar 16 2023, 1:56 PM
F34026050: Screen Shot 2021-01-26 at 2.12.09 PM.png
Jan 26 2021, 1:25 PM
F34022415: bug.png
Jan 25 2021, 2:45 PM

Description

Steps to reproduce

  1. Go to https://meta.wikimedia.org/wiki/Schema:PrefUpdate
  2. Click on the red button "<>" at the top right of the page

Expected result
A popup menu appears over the JSON table

Actual result
The popup menu appears under the JSON table, as in the screenshot:

bug.png (768×1 px, 115 KB)

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript

I was about to report this....

I found T249557: EventLogging revision popup gets hidden behind content in Timeless which may suggests this worked in Vector skin at the time. It currently works correctly in MonoBook. It works in the Timeless too because of the fix in the linked task, but I think the fix for this should be in the EventLogging extension instead of requiring every skin to do what Timeless is doing. The toggler also needs tooltip, because I was wondering what it does before clicking and expected some explanation.

Screen Shot 2021-01-26 at 2.12.09 PM.png (746×1 px, 225 KB)

@He7d3r, @Ammarpad: Please could you add information about which browser you're using when you see this.

I see the following in Google Chrome (111.0.5563.64) whilst using the Legacy Vector skin:

Screenshot 2023-03-16 at 13.45.56.png (2×3 px, 1 MB)

However, I do see something like it whilst using the Vector 2022 skin. In this case, I had to disable the .vector-body-before-content { overflow: hidden }; rule (added in T325391) to get this to work, i.e.

Screenshot 2023-03-16 at 13.47.35.png (2×3 px, 1 MB)

@phuedx, my comment was added over 2 years ago, so it's not surprising the issue has been fixed in the meantime. I was using Google Chrome at the time I uploaded the above screenshot. It's fixed now in Vector, but yes, it's still an issue for Vector-2022

Also your second file is not attached to this task, so it's not visible.