namuit / phamlp

Automatically exported from code.google.com/p/phamlp
0 stars 0 forks source link

Some new css3 selectors don't work. #112

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Hi, I tried to use these new css3-selectors, but without success:
   button::-moz-focus-inner  
   td.small:not 
   tr:nth-Child(2)   
   tr:nth-last-Child(2)
   input:valid
   input:invalid
I got the error-massage:
   Oops, an error occurred! <- I think is Typo3
   Properties can not be assigned at root level.

What steps will reproduce the problem?
1. I use the typo3 extension sassify, phamlp is intigratet there
2. I have noticed this, if I tried to use a reset.css file from a html5/css3 
framework, with some of the seletors above
3. After deleting the css3 selctors everything works fine.

What is the expected output? What do you see instead?
   Oops, an error occurred! <- I think is Typo3
   Properties can not be assigned at root level.

What version of the product are you using? On what operating system?
I thing it is the last one, because the extenstion sassify was recently 
updated. In which file I can see what version is used?

Please provide any additional information below.

---

I don't know were the problem is - phamlp or the typo3 Extension. I try to find 
it out. So this post is a generally question, if it is a known bug in phamlp or 
not.
Regards

Original issue reported on code.google.com by arno.pfe...@gmail.com on 5 Nov 2011 at 12:29

GoogleCodeExporter commented 9 years ago
ext:phamlp has the same problem due to errors in phamlp :(

Original comment by kay.stro...@gmail.com on 8 Nov 2011 at 12:38

GoogleCodeExporter commented 9 years ago
Hi, I have written this problem to the orignal SASS Developer (Ruby). Here is 
the answer:
   Those are definitely valid Sass.... at least SCSS. Sass you might need to
   put it  on the same line.

   I'm not really familiar with PHamlP, except that I know that its an engine
   for PHP. I'd try contacting the authors of that language with this issue.

   Certainly, if its SCSS, all CSS is valid.

   -hampton.

So, we should hope, that these error is fixed soon.

Original comment by arno.pfe...@gmail.com on 11 Nov 2011 at 4:56