Issue with "BigInt": Left sidebar blends with text
See original GitHub issueMDN URL: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/BigInt
What information was incorrect, unhelpful, or incomplete?
The left sidebar clips with the actual text and makes it hard to read.
Specific section or headline?
Most noticeable near the Operators heading.
What did you expect to see?
Sidebar separated by whitespace
Did you test this? If so, how?
N/A
MDN Content page report details
- Folder:
en-us/web/javascript/reference/global_objects/bigint
- MDN URL: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/BigInt
- GitHub URL: https://github.com/mdn/content/blob/main/files/en-us/web/javascript/reference/global_objects/bigint/index.md
- Last commit: https://github.com/mdn/content/commit/05a80e13f9824c8733ed293c5f22e322248096ef
- Document last modified: 2021-12-03T05:27:53.000Z
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
“ERROR: operator does not exist: integer = text” how to fix it?
First answer and the best way to solve the problem is: fix the code. Check which value should be cast to which, and...
Read more >`array_agg` throwing "could not find array type for data type ...
`array_agg` throwing "could not find array type for data type bigint[]" ... What's happening? Is there a better way to approach this problem?...
Read more >Safari Technology Preview Release Notes - Apple Developer
Fixed an issue where browser.tabs sometimes returned an incorrect URL for pinned tabs. Bug Fixes. Fixed the Share Menu when sharing an image...
Read more >About Implicit Text Casting in Greenplum Database
This example query that compares text and non-quoted integer returns an error. SELECT * FROM bar WHERE b = 123; Adding an explicit...
Read more >bigint primary key postgres - tuvanacc.vn
The simplest way to fix this is to define the new column in fixtures. If you don't need 64 bit integer for your...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yes. Code blocks by default have that(
word-wrap: break-word
) style.That does work, but not as good as it does in firefox.
Edit: found similar issue in mdn/yari#4635
The simple solution here would be to remove the
word-wrap
property on.sidebar code
.It looks fine on firefox(wrapping the text to next line at-word). Issue seems to be with chromium browsers.
It’s because the text is within the code block and chromium browsers for some reason arent able to figure out where to wrap text within
<code>
.