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.
Related
I'm trying to upgrade from an old TinyMCE 4.9 installation to the current version 6.3. It looks like somewhere between those versions, TinyMCE started writing line break tags as <br> instead of <br />. But I have 12 years of user data that uses <br /> and a large, multi-platform system that relies on that format for parsing. Is there a way to revert to the previous format?
A common answer to questions like this is to do my own post-processing to change any TinyMCE formatting I don't like, but one reason I'm upgrading is to reduce the number of hacks like this that I'm already using. This one would be especially confusing because <br> would be used in several editing functions on the web platform while <br /> is used everywhere else.
This seems like it would be a breaking change for a lot of users, so I'd be surprised if there isn't some built-in way to adjust it. But I've searched the web, the TinyMCE docs and the source code with no luck. I can't even find a mention of it being changed in the change log.
I did find references to a closed configuration option that might be what I want, but only in 8+ year old posts, and this option no longer appears in the documentation. I took a guess and tried adding closed : "br" to my configuration, but it didn't make a difference.
Oh, while searching the GitHub issues I found a solution! The element_format configuration option with a value of "xhtml" restores the previous formatting of singleton tags:
element_format: 'xhtml'
The change log shows that the default value for this option was changed to "html" in TinyMCE 6.0.
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.
This question already exists:
how to hide chrome extension apps in "chrome://extensions/"?
Closed 8 years ago.
Basically this question for chrome,
"How to create hidden Firefox Extension?".
Thanks
First off, it sounds like you're trying to build malware. If that's not the case, I'd suggest you clarify your intent.
However, it sounds like the closest thing to what you're looking for is Chrome's "Enterprise Policy" system. It's meant for use by large organizations to centrally manage hundreds of Chrome installations remotely, but it's also popular among malware developers (for the same reason). Your extension won't be "hidden," since Chrome doesn't allow for hidden extensions, but the user won't be able to uninstall it through chrome://extensions.
I've never worked with it before, so I can't give much more detail, but here's a link to a Google page that explains it a bit.
Again, you should really reconsider whatever it is that you're doing. If you need your code to be invisible to its user, you're probably doing something you shouldn't be.
Make a chrome app instead of an extension. It will appear in the apps window but not in the extensions window. I don't know of any other way. Chrome is fairly locked down.
This question already has answers here:
Closed 10 years ago.
Possible Duplicate:
is there any limit on css file size?
I have a generated CSS file coming from a third party application of around 60K lines with ~ 13K classes defined in that. I cannot change the generated CSS file by any means on the server (when it is generated from the third-party application) and the way it is injected in different HTML files on GET requests.
My target browser for the application is IE9 and it so happens that IE9 is failing to parse more than 4095 classes coming from one file and hence doesn't get the classes defined after that. Also, this number has been exact while debugging the generated file I have and another test file which I created (gist below) to verify this number.
Is there any workaround possible or am I missing any detail here ?
Illustration:
To give a quick way to reproduce this problem, here is a link to a gist that I have created. Just extract all the files in some folder and open ie9_test.html in IE9
https://gist.github.com/3941331
I couldn't find any service to show the output online where an IE9 environment is present. My IE9 build is 9.0.8112.16421
EDIT: The test files and my files work fine on chrome v22
Well one obvious workaround would be to break it up yourself into two or more files. You could then include both on the relvant pages. You would just have to write a simple css parser to identify where to cut up the file. And by simple I mean just find where classes start and begin so you know where to chop chop.
This question already has an answer here:
Closed 10 years ago.
Possible Duplicate:
Pinpointing the difference and changes made between two pages in magento 1.6.2
http://dokha.co/index.php/shisha-tobacco/al-fakher-shisha-tobacco-108.html
As you can see from the link above the product page is disorganized to some degree.
I have made some modifications below, in firebug, and took a screenshot. Can anyone advise on how to put these changes into effect?
You are trying to move up the "Select a Flavor" block?
Look at the source and delete the DOM node <div class="clearer"></div>. I use google Chrome browser because it is very easy to do things just like this. I right-clicked on Select a Flavor then selected Inspect Element. In the lower pane, I navigated up until the clearer block and deleted that.
To make the css changes to your page. Please create a custom.css file in the skin/frontend/yourfolder/css/custom.css and add the styles which you made in the browser.
Personally, I use Google Chrome browser to make changes to the page and then copy into the customised .css file.
It is always best practise not to replace in the default .css but use a customised version, so you have a version of the original file.
Hope it helps.
Cheers