User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:126.96.36.199) Gecko/20110319 Firefox/3.6.16 Build Identifier: I have created a google docs drawing at the demonstration URL: Double-click the bottom-left red box: an edit box will appear - the edit box might, or might not, appear fully, i.e. it might run out of the page page and part of it may be hidded - if the edit box will show up in full, then close it and double click the top-right green box: and edit box will appear. Just close it, and... - go back and double-click the bottom-left red box: the edit box will appear, and again it might, or might not, be fully visible. - repeat this process (i.e. double-click the bottom-left red box and then close its edit box, then double-click the top-right green box and then close its edit box) several times; eventually you will notice that the edit box that openes when double-clicking the bottom-lef red box will be only partly visible A couple of remarks: 1) first of all, if a new element is added to the page (programatically), and this new element turns out to run over the page limit, how comes that no scroll bar is shown in the main window (so that you can scroll down and see the entire element)? i mean, at the very least, this is what one would expect, isn't it? when you have some stuff on a page, you want to be able to scroll through the *entire* page content 2) however, there's another problem here: apparently the "why no scroll bar when a new element is added and runs out of the page" problem is not what comes into play in the google drawing shown at the demo URL: on chrome, there is no scroll bar added to the page, but rather the elements inside the page (the "canvas" of the google drawing) gets shrinked when the edit box is displayed for the bottom-left red box. What i'm trying to say is that, while the "why no scroll bar when a new element is added and runs out of the page" is valid, this google drawing reveals yeat another, different, problem in firefox, or at least it definitely behaves differently from chrome. 3) it's weird, but safari, allegedly also based on webkit, has some bizarre in-between behavior between fx and chrome: while on chrome the edit box is consistently displayed properly, and in fx it's consistently displayed only partially (after the first time it's displayed partially), in safari it's displayed once okay, then only partially, then okay again, then partially again, etc Reproducible: Always Steps to Reproduce: see description above
Correction: inside "A couple of remarks" above, at point "2) however, there's another problem here: [.....]" i made a mistake: i said that: "on chrome, there is no scroll bar added to the page, but rather the elements inside the page (the "canvas" of the google drawing) gets shrinked when the edit box is displayed for the bottom-left red box" I just double-checked that and it's not like that: instead, when the edit box is displayed at the bottom of the page, it is always fully visible because the entire page gets *scrolled up* (i.e. you will notice that for the edit box to be fully displayed at the bottom, the elements at the top of the page are scrolled outside of window view). So apparently what happens in both chrome and fx is that the page with the programatically added edit-box is too large to fit the browser window; the only difference is (apparently) that in chrome the page is automatically scrolled such that the selected element - the edit box - is fully visible, while in fx this is not done. ------ My guess: probably everything that is shown inside a google drawing window is actually inside some sort of a DIV element, and this elements has disabled scrollbars, so it probably all boils down to automatically scrolling the content of a container element such that an element contained in it (the edit box) is fully visible when selected
Confirmed on Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:188.8.131.52pre) Gecko/20110418 Namoroka/3.6.18pre Mozilla/5.0 (Windows NT 6.1; rv:6.0a1) Gecko/20110418 Firefox/6.0a1 The edit box of bottom left red box runs out of the page and is partially hidden.
> if a new element is added to the page (programatically), and > this new element turns out to run over the page limit, how comes that no > scroll bar is shown in the main window Google docs explicitly disables the main window scrollbar by styling the <html> element as overflow:hidden. If I make my window short enough I can reproduce the edit box not being scrollable to, of course, but that's just how the google docs page is designed. Seems like a bug they should fix. In Chrome, I don't even see the edit box come up.