I have been using the below link format for the past few years to download crx files from the chrome store.
https://clients2.google.com/service/update2/crx?response=redirect&prodversion=[PRODVERSION]&x=id%3D[EXTENSIONID]%26uc
Since last week this method no longer appears to be working for me, has anyone else encountered this and found a way around it? has this method become deprecated?
As you can see here:
https://stackoverflow.com/a/67453990/1049870
The x parameter has changed a lot.
Related
This question already has answers here:
Some Emmet abbreviations in VSC not working, like '!' or using '*'
(8 answers)
Closed 7 months ago.
I have started to use Visual Studio Code and am having issue's with Emmet.
When I type in the code ul>li and hit tab to expand, it expands. But when I try to multiply the code like ul>li*3, it does not expand and I get no suggestion for that abbreviation. I have added "emmet.triggerExpansionOnTab": true to the json file, and that did nothing, and I have restarted all extensions with the restart extension host command.
All suggestions on how to fix this issue are appreciated.
Yes, I am facing this issue too since latest update.
Somehow the solution I have got is :
You can check the box “Emmet: Use Inline Completions”
In settings by typing “emmet” in the setting’s search.
After checking the box You can see the suggestion and choose it by pressing the tab.
This is the solution I have got till now but hoping that we could have the previous version back.
You can get them back consistently by turning Inline Suggest on.
If you find that annoying or distracting, you can leave that off and use ctrl+space to get the old popup shortcut to come up, and then hit tab as normal.
I have written a C# code that calls Google Chrome to load a specific url on the computers local hard drive. The C# code already encodes the URL (replaces space characters with %20) and this used to work fine until a couple of weeks ago that this issue started happening!
The quickest band-aid seems to be modifying the C# code to not replace " " with %20. But the Chrome behavior may change in the future or some customers may not have the same version/settings of the chrome installed.
I think the sustainable solution is to Tell Chrome to either Encode or not encode the URL. Now my question is:
Is there a Chrome switch that enforces it to either translate the url or ignore it?
Does it have a setting or option for this?
I have found a couple of lists with Chrome Switches Here and Here. However both of these lists are incomplete and refer to this reference. I have Ctrl+F'ed for "URL" and "URI" but did not come across a relevant answer.
Thanks in advance.
I have already asked this question on Super User, however I think
people in this forum has more expertise on solving these types of
issues. (Also after 24hrs, the question in Super User has not received
any feedback at all!)
There is no Switch for it, however, as HexBolt has stated adding the "file://" tells Chrome that the url is already translated. Please see his extension to the answer for this question.
This question already has answers here:
How to check for duplicate CSS rules? [duplicate]
(3 answers)
Closed 6 years ago.
I've been using the "Emmet Livestyle" plugin lately, and its been flawless. But on the last commit to my github project I noticed that the css lines were duplicated* from 1446 to 3448. I then opened chrome dev tools and confirmed that there were like 3 same styles per one element. I suspect that plugin is the culprit to this problem.
I really need to remove the duplicates. But I don't know where they start or where they end as the file is pretty large.
Could you guys happen to know any online tool or sublime plugin that could help me with this ?
Thanks.
I've had this exact same problem with LiveStyle with my files being duplicate somewhere around 4 different times. One file is now 4 times as long.
In searching for a solution I found a NodeJS plugin called css-purge. It IS the solution and as far as I know, the only solution. I guarantee it.
You can find it here CSS Purge Package Install Page. Be sure to install NodeJS properly on your system first. I'm on a Mac so these were my instructions. I'm still looking for a solution for fixing Live Style. It used to work flawlessly until this new dedicated app started causing problems.
If you look at Chrome's Developer Tools (other browser's do this as well), you will be able to, not only see what styles are being applied to an element, but from where those styles are coming from:
Once, you know the source, a simple "Find" operation in your editor will track the rule down.
The console gets stuck in a state where every two page refreshes a new closed instance of my indexedDB is displayed. They are all closed except for the one on the top and everything within the application still seems to function normally, however other strange things occur when using the console.
When I click on a table within the database it shows the data, but when I try to filter or go to the next page it all disappears. I have to completely close the browser tab and then reload.
Sometimes when I enter in console commands they don't do anything, don't return anything (not even undefined), but when I refresh the page it alternative between working and not working.
Let me know if you need some more information. I haven't a clue what's causing this. I'm using the latest version of Chrome 35. Any thoughts?
Saw this once. Try a fresh install, and if that does not work, try upgrading to dev channel 37. I did both those things (for other reasons), but have not been able to reproduce the bug since. Trudging through Chromium's list of open issues or changes might also help.
Also, it looks like your question is not really about programming so it might be closed. There are other 'something.overflow' sites to post this type question.
Edit: also, regarding the disappearing issue, I actually reported this bug on Chromium. It was recently fixed!
I have an old FBML app that uses fb:submit. When I was trying to make a few changes to it I noticed that the fb:submit buttons aren't functioning and I'm not sure whats happened here.
FBML is deprecated, but anything which was already working should still be - if you're sure that this is not a problem on your end there may be a bug with the FBML - if so, please file it at http://bugs.developers.facebook.net
You should absolutely be migrating away from FBML. Facebook has expressed interest in removing it entirely from the Platform by the end of the year.
Opening a bug will likely not be addressed or fixed due to the deprecation of FBML.