search

thoroc / scriptno

Automatically exported from code.google.com/p/scriptno
1 stars 0 forks source link

ScriptNo window is truncated on newer version of ChromeOS #104

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Upgrade ChromeOS to version 20.0.x
2. Click ScriptNo button to view blocked/allowed domains
3. Note that the window is truncated, showing only a bit of text and the Allow 
button, rather than all domains on the site.

What is the expected output? What do you see instead?
Expect to see a full pop-up window/bubble, not a cut-off, trunated version.

What version of the product are you using? On what operating system?
ScriptNo 1.0.6.2 on ChromeOS 20.0.1105.0

Please provide any additional information below.

Original issue reported on code.google.com by jeffrey....@gmail.com on 23 Apr 2012 at 2:51

GoogleCodeExporter commented 9 years ago 
I also see this issue running with 19.0.1084.30 beta ChromeOS

Original comment by stuart.k...@appogee.co.uk on 25 Apr 2012 at 9:14

GoogleCodeExporter commented 9 years ago 
Also noticed under Ubuntu Linux 10.04.
the ScriptNo window renders the appropriate width, but only partially, 
vertically (such that only the "Allow" button is clearly visible). The full 
content of the window exists, but is invisible. ONLY IF you hover over the 
allow button text until a tooltip displays, the pointer will reveal more of the 
window's content if moved about, creating the effect of "painting" the window's 
contents into view.

Google Chrome   19.0.1084.56 (Official Build 140965)
OS  Linux
WebKit  536.5 (@119244)
JavaScript  V8 3.9.24.29
Flash   11.1 r102
User Agent  Mozilla/5.0 (X11; Linux i686) AppleWebKit/536.5 (KHTML, like Gecko) 
Chrome/19.0.1084.56 Safari/536.5

Original comment by andrew.s...@gmail.com on 27 Jun 2012 at 9:11

GoogleCodeExporter commented 9 years ago 
I have noticed this as well in the extension. It can take numerous clicks on 
the icon to get it to open properly.

When I first installed this extension, the issue didn't start immediately but 
after using the browser for a few minutes, it started to happen.

Original comment by tre...@vancouverdrivers.ca on 11 Jan 2015 at 12:28