[GitHub] [royale-compiler] carlosrovira opened a new issue #154: CSS processing order matters

[GitBox <gi...@apache.org>]

carlosrovira opened a new issue #154:
URL: https://github.com/apache/royale-compiler/issues/154


   Hi,
   
   while doing Jewel SimpleLoader component I discover the following css rule:
   
   ```
   .jewel.loader {
       border: 16px solid #f3f3f3
       border-radius: 50%
       border-top: 16px solid #3498db
   }
   ```
   
   doesn't work as expected. The "border-top" is output before "border" and this make it border takes precedence, while if we left the current order, the browser finds first border and then border-top so making the border top blue instead of grey.
   
   Workaround for now is:
   
   ```
   .jewel.loader {
       border: 16px solid #f3f3f3
       border-radius: 50%
   }
   .jewel.loader.segment {
           border-top: 16px solid #3498db
   }
   
   butis very limiting and cumbersome.
   
   I think we're doing some kind of rule ordering while processing, since no matter how I define the CSS, I get always the same order. I think we should prevent any ordering to avoid this kind of problems that are valid CSS and becomes invalid.
   
   ```


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org