-
-
Notifications
You must be signed in to change notification settings - Fork 32.4k
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
[docs-infra] Additional white space left after expanding the code block #39272
Comments
Hello! I'd like to take a stab at this issue if possible? |
@jpettis1 Yeah, go for it! Want to share how you're thinking about tackling it beforehand? |
This is the space reserved for the ad. It looks like If there are really no ad that we can fetch after 10 attempts (current threshold), we could use the space with an in-house ad. If ads are disabled, the space isn't allocated. |
Though it shouldn't be there when there's no ad, right? |
I think it's just their is no add, because the JSON returned by the API query does not contain any link except one to the carbon branding page. Plus I managed to see one.
Sounds a good idea SHould be fixed by #39285 |
Got it! I was taking a look at the src code this morning, but sounds like issue will be resolved. Thank you! |
@alexfauquette normally, we try to query an ad with up to 10 network requests. When I opened the network panel, I could only see one attempt. The logic was copied from https://github.com/Semantic-Org/Semantic-UI-React/blob/master/docs/src/components/CarbonAd/CarbonAdNative.js |
Maybe because it succeeds in getting an ad π More seriously, I can't reproduce what you describe. here is a screenshot of the preview with no add found (10 requests sent) Here is another one with 8 requests (the last contains an ad so it stopped) |
Steps to reproduce πΉ
This problem can be seen in any component page β for example, Material UI's Button page.
Expected behavior π€
The additional white space shouldn't be there β content spacing throughout the page should remain the same.
The text was updated successfully, but these errors were encountered: