-
-
Notifications
You must be signed in to change notification settings - Fork 377
fixed table overflow of json Data Types table #2019
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
fixed table overflow of json Data Types table #2019
Conversation
|
Hi @unnati-jaiswal24! Thanks a lot for your contribution! I noticed that the following required information is missing or incomplete: issue reference, kind of change description Please update the PR description to include this information. You can find placeholders in the PR template for these items. Thanks a lot! |
built with Refined Cloudflare Pages Action⚡ Cloudflare Pages Deployment
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2019 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 30 30
Lines 633 633
Branches 196 196
=========================================
Hits 633 633 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Hi @unnati-jaiswal24! Thanks a lot for your contribution! I noticed that the following required information is missing or incomplete: kind of change description Please update the PR description to include this information. You can find placeholders in the PR template for these items. Thanks a lot! |
|
Hii @unnati-jaiswal24, great initiative towards this issue , can you please share visuals after changes, it makes easier to look into it. |
|
Hi @unnati-jaiswal24! Thanks a lot for your contribution! I noticed that the following required information is missing or incomplete: issue reference, kind of change description Please update the PR description to include this information. You can find placeholders in the PR template for these items. Thanks a lot! |
1 similar comment
|
Hi @unnati-jaiswal24! Thanks a lot for your contribution! I noticed that the following required information is missing or incomplete: issue reference, kind of change description Please update the PR description to include this information. You can find placeholders in the PR template for these items. Thanks a lot! |
|
Hi @unnati-jaiswal24! Thanks a lot for your contribution! I noticed that the following required information is missing or incomplete: issue reference Please update the PR description to include this information. You can find placeholders in the PR template for these items. Thanks a lot! |
What kind of change does this PR introduce?
Bug fix & UI enhancement — makes the JSON Data Types table responsive on mobile and removes the need for horizontal scrolling.
Issue Number: #1623
•Closes 🐛 Bug: Table in JSON Data Types page not adjustable for mobile #1623.
Others?
None.
Screenshots/videos:
Old view (table cut off, requires sideways scrolling).
New view:
json-data.tables.mov
(table fits the viewport and is fully readable).
If relevant, did you update the documentation?
Not applicable — this PR only updates layout and responsiveness of an existing page.
Summary
This PR fixes the mobile layout of the JSON Data Types table, which previously appeared cut off and forced horizontal scrolling to read all columns. It updates the table container styles to behave responsively on narrow screens, ensures long cell content wraps correctly, and lets the table height grow naturally so it stays within the visible area on mobile devices. Desktop behavior remains unchanged.
#1623 , fixes #1623
Does this PR introduce a breaking change?
No — this PR does not introduce any breaking changes. The updates are purely visual/responsive and do not alter existing data, APIs, or functionality.
Checklist
Please ensure the following tasks are completed before submitting this pull request.
Read, understood, and followed the contributing guidelines.
Tested the changes on: