In my browser extension, I am trying to upload a file from my computer. When I click on "select a file" option inside my browser (), the file selection dialog box underlays behind the popup window.
This appears only when the browser is in full screen mode and on MAC OS. Once I switch the tab or remove full screen mode it overlays as expected.
Can someone please provide a solution or workaround to this issue?
I encountered the same issue recently with a Chrome extension. How did the issue appear? I don't think I've changed anything, it seems to have appeared out of nowhere.
If you have any insights, I'm interested in collaborating with you to debug the issue with my own extension. Let me know!
Related
Maybe a stupid question. I'm new to TradingView and pine script, so please bear with me if there's some simple way to do this...
I figured out how to copy and modify a script from the library. At first, I could see a tiny edge of a window at the bottom of the script. When I saved or attempted to add the script to the chart, the window showed whether the script processed or had errors.
Now, though, I seem to have "lost" that window. How can I display that window? Also, once displayed, how can I make it larger?
Edit:
Here's a screenshot of the bottom of my editor -
Right-clicking on the console (errors) window showed a little pop-up saying:
While my cursor is in the editor window, holding Ctrl (or Cmd on a Mac) plus the backtick key toggles the console window open and closed.
Now, I can see the console log window whether I have errors or not.
you can show/hide the pane with pine scripts with the "_" icon on the right side:
show
hide
On the rigt side next to the "_" icon you can toggle/maximize the pine script window.
Add any error to your script and save the script.
In the lower left corner, you will see a small gray triangle.
Drag it up with the mouse.
The "Show console" was never visible in my browser. Only the "Toggle console", which did not do anything for me.
I tried a different browser and the console showed well. So I figure it was the browser I was using "Firefox".
So, I re-started Firefox, by going to Un-install Programs in Windows, clicking "Remove program", in front of the Firefox logo, which gave me the choice to restart Firefox. I did took that choice and this fixed the problem for me. I hope it helps others.
On Firefox, it may bug and never show it even with the shortcuts (because it becomes a tiny single-line that can't be dragged at the bottom of the page).
In order to fix it without uninstalling firefox: clean the site data for the domain.
According to Google this can be accomplished by visiting "chrome-devtools://devtools/devtools.html" in Chrome but now visiting that page in the stable version of Chrome (or Canary), just shows a 99% stripped version of the inspector.
To reiterate my "title" this is in reference to "inspecting" the inspector. Not just inspecting a normal webpage.
And while I don't think it's necessary to know to resolve the issue, I"m inspecting the inspector so I can style it as discussed by Paul Irish and here: https://darcyclarke.me/articles/development/skin-your-chrome-inspector/
Follow these easy steps!
Press Command+Option+i (Ctrl+Shift+i on Windows) to open DevTools.
Make sure that the developer tools are undocked into a new window. You may have to undock from the menu:
Press Command+Option+i again on this new window.
That will open the DevTools on the DevTools.
You can redock the page's DevTools if you want.
If it's not already, select Elements — it's the first icon at the top of the inspector.
A little beyond the scope of your question, but still valid in understanding why you're experiencing your problem can be found by understanding how Chrome Developer Tools: Remote Debugging works.
Open chrome://inspect
Open the inspector on that page (cmd + alt + i)
Scroll to the bottom of the page, under the Other section click the inspect link
The URL in the Other section should look something like this:
chrome-devtools://devtools/devtools.html?docked=true&dockSide=bottom&toolbarColor=rgba(230,230,230,1…
EDIT: they've fancied up the chrome:inspect page so you have to click the Other header on the left to get this to work now.
I just got this to work. The key is that you have to start up chrome in 'Remote Debugging' mode.
on OSX, open an terminal window and execute the following:
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --remote-debugging-port=9222
On windows, Its
chrome.exe --remote-debugging-port=9222
(better windows instructions can be found here: https://developers.google.com/chrome-developer-tools/docs/remote-debugging#remote)
This will start up an instance of chrome, that will send debugging messages to a local webserver on port 9222.
If you access that web service, it will give you the ability to use the inspector to inspect any chrome window that is running. Since we want to inspect the inspector, we need to start an inspector window first (As above Use the shortcut keys; for Mac it's Command+option+i.)
Now, go ahead and navigate to
http://localhost:9222
It will present you with a list of windows to display in the debugger. Select the window that starts with "Developer Tools" and you'll be able to inspect the css for the inspector.
Its hard to see in the image below, but on the left I have my chrome window pointing at the remote debugger, highlighting one of the toolbar labels. On the right you see it lit up with the tooltip just as if we were debugging a web page.
A few weeks ago somebody pointed this out in stackoverflow's "javscript" chatroom. First, and very importantly, make sure the inspector is undocked from your browser window. Then it's just a matter of opening a inspector window and then inspecting that window. In windows it's CtrlShiftI (Edit: I said, CtrlShiftI but that brings up the console inspecting the console... you should be able to navigate back and forth.) for the keyboard shortcut. (Other keyboard combos for other options and OSes here and here.) Just do that twice and you're good.
Edit: ok, you're probably confused as to undock the window. This is what you'd click if it's docked..
Edit II: I'm not quite sure why you can't inspect. JDavis's answer is consistent with the Google Docs for Apple computers. If you're using Linux it appears to be the same as Windows. You supposed to hit the inspector key combination while the focus is over the inspector window.
I'm trying to display overlay icons on specific set of files in explorer window.
I have written shellextensionhandler class which has ismemberof(),getoverlayinfo() and getpriority() functions and it works fine if I open a new window in explorer, all these APIs are getting hit and overlay icons are getting displayed.
However, if I try to open a dialog box from any application, none of these APIs are getting hit and hence overlay icons are not getting set for files inside dialog box. And also I have observed that if I open dialog box it is not showing under explorer app (probably because of that reason since it is not treated as explorer window, for dialog box these APIs are not getting hit). Could anyone please provide solution on how to implement this?
The problem is with our code, where we are ignoring dialog boxes. Thanks Denis for helping. As Denis mentioned handler works correctly in Explorer if it is installed properly.
Clicking on the ellipsis link next to the issue, e.g.
I get a little light-bulb icon with an x
in the lower right hand side of my window. If I click on a link for duplicated code I get a similar x icon. Why is this? How do I fix this?
This turned out to be a browser problem. I refreshed Firefox and the lightbulb icon now expands to a window showing the correct information. Refreshing Firefox also fixed a persistent "Still Working..." problem where no menus, etc. were available after I installed SonarQube on a new server.
I am using Firebug with Firefox 3.6 on OSX 10.5.8. Since FF 3.6 there is a shortcut to activate fullscreen mode which is "shift" + "command" + "F". But it is the exact same shortcut of Firebug to launch "Display Element Information".
Since i never and don't really need fullscreen mode and use extensively the "Display Element Information" feature of firebug; i am trying to either change the firebug shortcut or disable the FF shortcut.
I tried finding something when accessing about:config but could not find anything relevant.
Does anybody has a solution or hack?
cheers
Change FireFox Shortcuts:
There is an extension called KeyConfig that allows you to change the keyboard shortcuts in FireFox. You can find it at the following URL:
http://forums.mozillazine.org/viewtopic.php?f=48&t=72994
Change FireBug Shortcuts*:
Open the FireBug Panel
Click the FireBug icon on the top left
Select "Customize Shortcuts"
Change the shortcuts you want then restart FireFox
*Note:
I am using FireBug 1.5
I am not sure if the option you want is in the list of shortcuts you need to change.
Hope this helps.
I think the shortcut you are referring to is actually part of the Web Developer plugin, not Firebug. Firebug has a simliar "Inspect Element" function that uses Ctrl-I.
If you don't want to install yet another plugin, just to change one shortcut, then you will have to change the Web Developer shortcut to something else.
I've tried overriding this behaviour using the OSX System Preferences, creating an Application-only shortcut to the menu item: Tools->Web Developer->CSS->View Style Information, but no dice. This plug-in, while one of the most useful that I've found, has always seemed kind of shoddy. It's rarely updated, and bugs seem to live on forever. It breaks every time FF is updated. etc etc. But I still love it.
Not sure which extension is causing this for you. Just checked Web Developer Toolbar and don't see Cmd-Shift-F anywhere.
One newer feature in Firebug is the Customize Keyboard Shortcuts preferences panel on the Firebug menu. Open Firebug, click on the Firebug bug icon menu in the top left of the panel and select Customize Keyboard Shortcuts from the menu that shows up. You'll likely need a restart for these changes to take effect.
Well, now i feel very stupid !!!!
Indeed it is a shortcut from the Web Dev Toolbar and not firebug. I used these 2 so much during a day of work that i forgot they are 2 separate add-ons.
I was able to change the shortcut via the "Options" menu of the Web Dev Toolbar.
And just in case someone changes a shortcut, remember to restart FF for the changes to take effect.
mea culpa.
But thank you every one for helping.
Case closed !