Skip to content

🐛 Bug: Table in JSON Data Types page not adjustable for mobile #1623

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

Open
idanidan29 opened this issue Apr 17, 2025 · 3 comments
Open

🐛 Bug: Table in JSON Data Types page not adjustable for mobile #1623

idanidan29 opened this issue Apr 17, 2025 · 3 comments
Labels
🐛 Bug Indicates that the issue is a bug or defect. Status: Triage This is the initial status for an issue that requires triage.

Comments

@idanidan29
Copy link
Contributor

Describe the bug

The table on the “JSON Data Types” page appears cut off when viewing from mobile devices and forces horizontal scrolling to read its contents.

Steps To Reproduce

  1. Navigate to the JSON Data Types page on a mobile device or resize the browser window to mobile size.
  2. Observe the table not adjusting to fit the screen, resulting in horizontal scrolling or content being cut off.

Expected Behavior

  • Cell content should wrap appropriately to prevent overflow.

Screenshots

Image

Device Information [optional]

- OS:
- Browser:
- version:

Are you working on this issue?

Yes

Do you think this work might require an [Architectural Decision Record (ADR)]? (significant or noteworthy)

No

@idanidan29 idanidan29 added Status: Triage This is the initial status for an issue that requires triage. 🐛 Bug Indicates that the issue is a bug or defect. labels Apr 17, 2025
@jagpreetrahi
Copy link
Contributor

Hey @idanidan29, I think this problem can also occur due to #1464. I think , if that one issue would resolve, then this one would automatically be done. What do you think about it?
Thanks

@idanidan29
Copy link
Contributor Author

idanidan29 commented Apr 18, 2025

Yes @jagpreetrahi , the original #1464 includes that problem, but since it was already a large issue effecting lots of pages with two types of fixes required, I separated them to make it more modular and easier to track.

@jagpreetrahi
Copy link
Contributor

Yeah, understandable it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 Bug Indicates that the issue is a bug or defect. Status: Triage This is the initial status for an issue that requires triage.
Projects
None yet
Development

No branches or pull requests

2 participants