[![][1]][1]
Hi! When switched to legacy editor this screen showed up and it makes impossible to switch back to new version as inactive button. I did sign off and sign in, it does not help. Any ideas how to get back to new editor?
[1]: https://i.stack.imgur.com/rz7Rp.png
What you are describing might in fact be a bug.
You may want to check this issue here on Google's Issue Tracker.
I suggest you star the issue here and eventually add a comment saying that you are affected by it.
Related
I can't find anybody facing the same problem as mine.
Every time I click an image on google image, suddenly the whole page disappear, but I'm still able to click things just like everything is still there.
I already turn off all extension, use incognito mode, after finally I try to use inspect element, and found attribute stating "Opacity: 0" on the body. And after unchecking the box (Quick disable attribute in inspect element chrome) everything shows up again.
I'm so confused on why this is happening.
Does anyone have ever facing the same problem?
Or how do I fix it?
It's so frustrating, because I have to refresh the page, every time I click on an image, or switch between images
so I was having this one. in the end, it was a virus.
In my case, it was showing an AD screen on the main google page, and in the sources>gstatic.com it had a different source which also was in a [unknown] source.
dug a bit up and discover some adware was using gstatic as a proxy to show ads on all browsers.
I solved it by running malwarebytes, it found it pretty quickly and solved it for me.
Posting this here because I'm hoping it helps people who search for this issue in the future.
part of the log
I started using Google Script a few hours ago, and I noticed that the Autocompletion doesn't not work correctly. It activates when I press ; (semicolon), but not when I press . (period).
Logger. // Does not display anything
Logger; // Diplays clear(), getLog(), ...
I am using an french AZERTY keyboard and I noticed that when I switch a QUERTY keyboard, then it works correctly.
It makes everything hard to do because, first I do not have the autocomplete, and also it inserts a method at the end of the line every time I press Semicolon and Enter...
Does anyone knows why I have this problem or how to fix it ?
Thank you!
Posting this for documentation purposes.
This behaviour was reported in Issue Tracker a few weeks ago. Users who are experiencing this and want to keep track of this case might want to click the star on the top left in the referenced page.
Reference:
Issue Tracker: Autocompletion dialog malfunctions on AZERTY keyboards
I'm sorry this question might not be completely on topic, but i couldn't find answers googling it.
I'm creating an google app script (with clasp).
When i run the script i get the following popup as usual:
I'm supposed to click on advance and go anways.
But the advanced button no longer works! it doesn't show me the followup button to continue anymore!
Does anyone have the same issue and was able to fix it? It seems to have originated after the chrome update (with rounded ui).
I tried deleting the original grant (i added a feature that needed bigger scope), but even that didn't work.
It might be one of my chrome extensions.
Doing the same thing in incognito mode, worked!
I am referring to the save feature in the 'Sources' panel of the Chrome Dev Tools. I have been using this feature for a long time in the stable release of Chrome, but after installing the build from the developer channel, I notice that once I have saved the file the first time, Chrome no longer prompts me to save and just does it automatically after every change I make.
This is quite a pain, as I make a lot of changes experimentally in the dev tools whilst debugging which I don't wish to save, I would like Chrome to save the file only when I explicitly tell it to.
Does anyone know if there is a way to disable this automatic CSS saving?
(Apologies for no screenshot, my PrtScn key seemingly won't operate when I am in a context menu)
Update:
I have reverted to the current stable build, 27.0.1453.93, and the behaviour appears to be the same.
I am having the same problem, I can only offer workarounds: use another browser, such as Firefox, for doing tests!
Alternatively you could launch another instance of Chrome with a different profile. You could also launch a Chrome "Incognito Window", it seems to not apply the filesystem mappings.
I normally use an Incognito Window or inline styles to test changes.
Alas, I learned after reading a post by Google's dev relations person
that the automatic save cannot be disabled and it seems that's the way
it's going to stay.
html5rocks.com/en/tutorials/developertools/revolutions2013
– tommypyatt Feb 21 '14 at 14:22
While not solving the issue directly, it is a decent work around:
In Chrome, in the css inspector you can click and hold the + button, then choose to add your changes to the inspector-stylesheet. It's not as convenient as directly editing in your css-selectors, but what you write will all be in inspector-stylesheet.css, so not saved to your project. Then when you are happy with your changes, you can manually put them in to your css.
I wanna use these very simple features in Google Chrome Javascript console but I really cannot find out how (already searched in official documentation,multiple videos and posts...)
Writing more than a javascript line! (currently after hitting enter, the previous code executes). Moreover, is there a way to make the 'writing' area of the console larger? (multiple lines)
Typical undo and redo edit. Currently control+Z does nothing.
really weird,
Thanks in advance,
Pere
The Javascript console really isn't intended to do serious development in, but it's pretty good.
Shift+enter will let you write multiple lines instead of instantly executing the code.