I'm working on a react project which has file names ending with .js, .tsx. However VSCode find references does not work on these files. It seems to work only on .ts files. Is there something I need to do in order to get this working?
In XPages, when I try to open a .js or .jss file, I often get just the tab wirh "Client/Server JS Editor" and nothing else, i.e. the file doesn't load. From the Navigator Eclipse view, I can open the same .js or .jss file using any other editor without problems. And then, it sometimes works, but I don't know yet when it does and when it doesn't. The other Editors are okay by the way, .lss opens nicely.
This behaviour I get for a few weeks now. Since it started I reinstalled Notes a few times, I upgraded to FP8, I also reinstalled Windows10 and Windows10 upgraded me to the Creators Update (with the fix, in the end). There's nothing that explains to me why the file doesn't show up on the screen.
Anyone familiar with this? Could you please tell me how to repair this?
Thanks!!
It's a bug introduced with FP8 that is fixed in FP8 Interim Fix 1. See this document for download options for FP8 IF1.
As a workaround you can do a clean/rebuild of the nsf and then use the SSJS editor.
Starting a couple of weeks ago....on some of our sites, but not all, when inspecting an element, the styles tab only shows the "styles box", but not the actual styles relating to css?? - Again, this is ONLY on some sites - weird
It should look like this (with styles showing on the right relating to css)
BUT......instead, on SOME of our sites, this just started a couple of weeks ago looking like this....with no css showing in the styles tab:
NOTE: it has worked for 2 years - The page looks fine and all styles are being applied to the DOM, but do NOT show up in the styles tab when inspecting element.
Any ideas??
I just had this same issue and to resolve it I went into Chrome Developer Tools -> Settings -> Scroll to the bottom and click "Restore defaults and reload" then it all magically came back!
I hadn't changed anything between it working and when it stopped so not sure why it broke but hopefully this helps you too.
I just close the tab, and reopen it, and then right click > inspect element. Don't need to restore the whole dev tools to default settings. It's a waste. Try it, it works! :)
I had to go to Chrome Developer Tools -> Settings -> Enable JavaScript source maps and then disable that checkbox. It has probably got do with sourcemaps and the fact that I'm building the scss to css.
something that worked for me: chrome:flags>Enable Developer Tools experiments>Disable. I had enabled it at some point, used it for years w/o issue, then could not see any style details as OP described. After updating, resetting devtools prefs to default, even trying incognito, this was the one thing that seemed to get it working again. There were some neat experiments, but i'd much rather be able to do my job...
I was also facing this problem, in addition to the suggestions the other users made it worked for me accessing:
Chrome Developer Tools -> CSS -> Relaoad Linked Style Sheets
Image Ilustrating the procedure
Another one for the mix - using CSS variables but one of the variables was referencing another variable that didn't exist.
Elements using that missing variable in the chain just don't show up in chromium at all (it hid all references to h2s in the case of my site).
Interestingly, it still shows the elements in Firefox's dev tool panel.
Look for errors in the CSS file, in my in my case it was on the global CSS variables, fixing the errors solved the problem.
This tool can help you find the errors:
https://jigsaw.w3.org/css-validator/
I was just having the same odd issue. I'm not 100% sure what triggered this to happen but we use build tools to build SCSS into CSS. I went into my CSS file and removed the source map reference -
/*# sourceMappingURL=myCSS.map */
And all of the sudden it started showing up again. Then I added it back and I can still see it. I am not sure if this is because a version of the map is cached now or not but this worked for me.
Even i faced this issue !!!
style.css file was causing this issue..
I just created a new css file (Ex: style1.css) and cut pasted the older css file content (all lines in style.css) to style1.css file. It works
Note: Don't forget to update link tag, which is loading css file.
I think your CSS files are not loaded properly. Just check the syntax for referencing the external stylesheets.
It should be like this
<link rel="stylesheet" type="text/css" href="mystyle.css">
If you are skipping the rel="stylesheet", browser may think it as a plain file. To confirm the loading of stylesheets go for Chrome Inspector -> Sources
Check the site resources
No need of resetting anything. Hope it helps :)
I use Dreamweaver and Breckets.
Could see that the problem occurred only when I used Dreamweaver.
Solved the problem by changing Dreamweaver's preferences
--> Code Format --> Line Break Type --> CR LF (Windows)
Sometimes it can be the server!
I just had this error on a page that appeared to be fully loaded but the style panel was completely empty.
A complete restart of Chrome (and verifying no processes) did not work.
Restarting my server (in this case a .NET Core app running locally in Visual Studio) then allowed the style panel to show.
I think there was some sort of connection leak or web socket limit - something of that nature which was confusing Chrome.
I think this may helpfull.. If it is an angular project > then simply run
ng serve --extract-css.
Is there a way to make Notepad++ autocomplete the CSS properties when working with LESS, like it does when working with CSS files?
Notepad++ supports autocomplete via the xml files in its ./plugins/API directory.
Download your LESS.xml or Here and add it to the directory, or better follow the instructions in the page.
I work for a company who's primary clients still use Internet Explorer 7 (NHS etc).
In our code we generate snippets of HTML in various places and Eclipse is generating lots of warnings relating to markup that is obsolete in HTML5.
I know that setting a valid doctype of HTML4 fixes the problem on flat html files but as we build the code over several PHP files we can't set a doctype in the snippets.
Is there a way to change the 'default' doctype to HTML4 globally or by project as I do not want to turn off the warnings as that may cause me to miss actual issues.
Drove me nuts too until I found the answer...
http://www.eclipse.org/forums/index.php/t/219788/
Steps:
Select an HTML file in the PHP Explorer. If there are no HTML files, create a new one.
Right-click > Properties > Web Content Settings.
Choose preferred doctype in the Document type list.
Click OK and exit Eclipse.
Open {your_workspace}/{your_project}/.settings/org.eclipse.wst.html.core.prefs with a text editor.
Replace document-type/{your_file_name}=... by document-type/<project>=... (do not modify <project>, paste it as-is)
Start Eclipse.