node.js api documentation display issue on Centos 6 with Chrome 36.* and FireFox 24.*

[ericlowry]

Hey I don't know if folks pay attention to stuff like this, but the docs don't render right on Centos with Chrome or Firefox:

The first letters are getting obscured...

It appears to be the #column1.interior { width: 749px; }

If I change it locally to width: 740px it appears to fix everything.

[ghost]

Same here with Arch Linux

[geek]

Same issue occurs with Safari on iOS

[doobix]

This is a weird one. I noticed this bug on my Mac Mini, however the page is totally fine on my MacBook Air and Galaxy S5.

[akhilpandey95]

I guess probably the window width is either wrongly adjusted in main script or the scaling is done on some other page which is making this page to look like that @seewes @wpreul

[SFantasy]

Same issue occurs on my OS X 10.9.4, Chrome 36.

[jaredhirsch]

Hmm, I'm able to repro the overlap bug on OSX Chrome and FF Nightly. Another related bug: on iOS, I'm not able to scroll to the bottom of the list of APIs at all.

Looks like the existing API page is framed under this new page, with overflow hidden, and left-positioned so that the old API nav menu is hidden. I think that's the reason for both of the bugs I'm seeing.

I'd like to help fix this bug, but I think the way to do it is probably not to tweak the CSS--it's probably to rethink the approach here. @fitzage, looks like you've been doing a lot of work on the blog recently; are you planning to address this at some point, or would you like help?

[akhilpandey95]

@6a68 Did you notice that the entire

is wrongly Implemented because when we scroll down not only the page gets stopped after we reach the bottom of page. What i mean is if we scroll down over API docs everything is fine until we reach the bottom of the page we can't scroll in the same direction upwards.

[ThisIsMissEm]

I suspect there may be a better way to implement this, which would be to change the way we build documentation for the website, and actually compile pages with the templates, rather than embed an iframe.

[fitzage]

The iframe is only a temporary measure. The proper method is complete and will be incorporated into an upcoming node.js version. Not sure which yet.

[ThisIsMissEm]

Ah, sweet.

[jaredhirsch]

@fitzage Great, thanks for the info. Mind bumping the iframe position over a few pixels in the meantime? :-P

[dongliu]

I assume the value 749px is too tight given the content width and flow right.