Hi 2 @ll!

I found a problem with the css 3.0 auto completion feature. I already discussed with the support about that and we need more opinions.

At first, the problem as is (in 6030 and lower):

When you activate "Code Settings -> Target CSS Version -> CSS 3.0" some of needed CSS 2.1 properties in completion list like "position, left, top, etc..." is missing.
The Problem is, W3 Definitations don't give use a really clear statement what is supported, and what not.
I think its better to list all 2.1 properties in 3.0 too.
So i post a part of my support email here why i think its better to list all CSS 2.1 properties even in CSS 3.0 list.



And what YOU think about that?

Greetz

If you are really targetting CSS 3.0 then I don't think that should include unsupported 2.1 properties, as it just causes confusion and people will continue using 2.1 properties even though they should not. Standards are important. Unfortunately CSS got into a mess because standards weren't (aren't) adhered to.

However, people might want to target 2.1 compliance, together with using some 3.0 capabilities that they expect to not work work in some browsers. A bit like the -moz- properties are used a lot and are ignored in IE.

So I think there should be an additional setting for 2.1+3.0 combined, so that people can choose 2.1, 3.0 or 2.1+3.0 The combined setting might lack certain support such as the new attribute selectors, which would be less likely to fail gracefully if not supported by a browser. However, that doesn't mean you can't use them, it just means they might be shown as an error or a warning.

Can an individual CSS file be targetted to a particular CSS version? If so, that might be a suitable compromise and would also be a tidy solution, so you would have a CSS 2.1 file for base styles then a CSS 3.0 file to override when the browser supports it.

I do realise a few people still use IE 6, but seriously, they should really upgrade and personally I no longer worry about supporting IE 6 too much as long as it doesn't break too badly.

The "2.1 + 3.0" Point is a good way i think.
This supports the standards of 2.1 and 3.0 seperatly or combined, which is very good compromise.
The currently workflow of most frontend developers for the design is to use CSS 2.1 and add some highlights with CSS 3.0.
Actual problem is just the missing support of browsers, mostly of them use own, not standard confirm, properties like -moz-xxx, -o-xxx, -khtml-xxx, -webkit-, filter:().... which anyway not in PHP Ed listed.
But that is Small Talk and Off Topic

And, about IE 6 Support, it was an example to underline my opinion

Whilst a bit tedious, bear in mind you can add your own CSS reserved words in the settings Editor > Reserved words > Language = CSS 2.1 I'd probably recommend not changing the CSS 3.0 reserved words, as it would be nice to keep those as standard.

Those keywords are stored in the XML file %APPDATA%\NuSphere\PhpED\config\hl.cfg so you could almost certainly copy that file around if desired.

I must admit that I do miss not having the -moz- and -webkit- reserved words myself.

you can add, modify or remove any properties listed in CSS code completion. In order to do this, you have to create a file in %APPDATA%\nusphere\phped\common directory. Its name shold be phped-XXXX.rel, where XXXX is your choise, and content should be according to main definitions in phped.rel. For example to add (or update) background-position with float,left,center,right,top,bottom content for CSS 2.1, you need to add only two lines below:

[CSS.CSS21]
background-position=float,left,center,right,top,bottom