PHP IDE :: NuSphere Forums :: View topic - phpEd reporting css attribute selectors with an error

Posted: Thu Apr 30, 2009 6:56 am

I've noticed that phpEd is giving me an error indicator for the code below:

<style media="screen" type="text/css">
input[class^='txt_'] {
color: rgb(255,0,0);
}
</style>

It places a red line under the c in class with the message 'Uexpected character in input'

Its definately phpEd displaying this error as I've also checked the file with HTML Validator 9 Std and it reports that the file is valid, also the online CSS validator confirms it as valid.

Posted: Wed May 06, 2009 3:41 pm

As far as I see CSS selector that you entered is not correct.
Probably you meant
input[class~='txt_'] {
instead of
input[class^='txt_'] {

and CSE would't find such errors, you're right

Posted: Thu May 07, 2009 1:51 am

The class~= indicator, I believe, is for matching a string in any part of the css selector:

a[href~="donkey"] - would match any a href link with the word donkey in it

others are:

a[href$="pdf"] - matchs an href that ENDS in pdf
a[href^="http://"] - matchs an href that STARTS with http://
a[href*="hello"] - matchs an href that has hello somewhere in it

links to the other sites are prohibited because of high spam activity

links to the other sites are prohibited because of high spam activity

Posted: Thu May 07, 2009 12:52 pm

all those variants are defined in CSS v3 standard which is not widely supported these days.

Posted: Wed May 20, 2009 1:20 pm

hmm .. in 2.1 we've:

Code:

[att] - has attribute match
[att=val] - exact match
[att~=val] - word match
[att|=val] - matches if attribute is "val" or starts with "val-"

http://www.w3.org/TR/CSS21/selector.html#attribute-selectors
all these are supported by phped.

further more

Code:

[att^=val] - start match
[att$=val] - end match
[att*=val] - wildcard match
(and many others)

are indeed css3 selectors
http://www.w3.org/TR/css3-selectors/#attribute-substrings

ie7 doesn't support it, ok.
so some webdevelopers may not know it, ok.
but we've ie8 now and ... and ... excuse me ? even firefox 1.5 did "[attr^=val]" -.-

arr ... k, later on.
but by the way - what about having the css 2.1 pseudo selectors in our code suggestion popup,
when we enter "#selector-xy" and press ":" ,
instead of suggesting html-tags (which is strange, because "tag:tag" makes no sense) ? ;O)

[edit]
and ... did you ever try to edit a css file with hacks in it, or humm ... look at this:

Code:

#foo, /* comment -> no error */
#bar
{
| /* -> press [suggestion shortcut], attributes show up */
}

#foo,
#bar /* comment -> error! */
{
| /* -> press [suggestion shortcut], html-tags show up */
}

i like phped to help me, even if the css isn't valid in its eyes.
by the way the example above is valid, according to jigsaw & the rfc. (whip me if im wrong =)
[/edit]

[edit 2]
IE7 supports all the selectors we're talking about...
http://www.google.com/search?q=css3+ie7
Looks like i'm stupid >.<
[/edit 2]

Posted: Sat Jan 16, 2010 11:59 pm

Is there planned support for CSS3 in the future? I just found that this code doesn't get recognized either:

Code:

::selection {
background-color: #E7EFD1;
color: #222;
}

::-moz-selection {
background-color: #E7EFD1;
color: #222;
}