Bug 500940 - CSS Unsupported Content in Editor (2016)
Summary: CSS Unsupported Content in Editor (2016)
Status: NEW
Alias: None
Product: WTP Source Editing
Classification: WebTools
Component: wst.css (show other bugs)
Version: 3.8   Edit
Hardware: All All
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: wst.css CLA
QA Contact: Nitin Dahyabhai CLA
URL:
Whiteboard:
Keywords: consistency, greatbug, investigate, usability
Depends on:
Blocks:
 
Reported: 2016-09-06 14:49 EDT by Kelly Ferrone CLA
Modified: 2018-02-22 11:33 EST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kelly Ferrone CLA 2016-09-06 14:49:58 EDT
The CSS editor always says, "unsupported content type in editor," when opening in the CSS editor. I have had this issue for more than two years and it started with Eclipse Keplar and I am now on Neon. I have had the issue on Windows 7, 8, and 10. Also on last three versions of Mac. Now I am on Fedora and one of my team is on Ubuntu and the problem always persists. Even though I re-make my eclipse every couple of months from scratch and install different combinations of plugins each time, the problem persists. 

To recreate the problem I simply try and open a CSS file in any CSS editor, even if it is a third party CSS plugin. 

I have discovered the problem is with Papyrus because the Papyrus CSS editor is literally the only one that works. When I uninstall Papyrus, the CSS editor works like a charm. This is a big problem because I use Papyrus a lot and I use CSS a lot, but never CSS for Papyrus. 

I can't even figure out how to just uninstall the Papyrus CSS anymore. In older versions of Eclipse, the CSS for Papyrus used to be a separate plugin, now it is part of the core and one can't uninstall separate of the entire Papyrus suite. 

Within the preferences for content types and file associations, removing every reference to Papyrus using CSS did not seem to do anything. 

The only similar bug reports I could find are all up to 10yrs old and completely irrelevant to my situation. 
 - https://bugs.eclipse.org/bugs/show_bug.cgi?id=128724
 - https://jira.appcelerator.org/browse/APSTUD-3185
 
From the above links I have discovered adding a content type like "*.csss" and then associating it with the CSS editor will get everything for CSS to work. No one is going to consider this a solution though. 

How has this never been reported before? Am I a rare case for using CSS and Papyrus with Eclipse? Anyone else experiencing this issue?
Comment 1 Kelly Ferrone CLA 2016-09-06 15:09:12 EDT
Ok, quick update on this. I tried uninstalling Papyrus, then while re-installing from "install new software," un-check the "group items by category," lastly check-off all Papyrus plugins except CSS plugins. Unfortunately the problem still persists even though I don't even have the Papyrus CSS editors which means it is another plugin within the Papyrus feature set. My next suspect is the xtext plugins.
Comment 2 Ernesto Posse CLA 2018-01-11 17:18:01 EST
I'm running into the same issue with 

  Papyrus for UML	3.2.0.201712060842	org.eclipse.papyrus.sdk.feature.feature.group

and

  Eclipse Web Developer Tools	3.9.1.v201711152154	org.eclipse.wst.web_ui.feature.feature.group

Apparently Papyrus includes its own CSS (Xtext-based) editor (a plugin called org.eclipse.papyrus.infra.gmfdiag.css3.xtext) but it is vastly inferior to the CSS editor provided by the Web Developer Tools project, so if one opens a file with that Papyrus CSS editor, you get a ton of errors on legal CSS. 

But even if one removes the Xtext nature in a CSS project and tries to open with the WTP CSS editor, you still get the "Unsupported Content Type" error, even though the preferences already list "*.css (locked)" in the CSS content type. In fact, there is only one *.css entry. 

Unfortunately there is no error log, and no output, even running as

eclipse -debug -console -consoleLog