1. #1
    Ext JS Premium Member burnnat's Avatar
    Join Date
    Jun 2011
    Posts
    414
    Vote Rating
    60
    burnnat is a jewel in the rough burnnat is a jewel in the rough burnnat is a jewel in the rough burnnat is a jewel in the rough

      0  

    Default SASS in 4.1

    SASS in 4.1


    A fairly frequent issue that people have been running into is that some of the syntax used in the default theme is incompatible with the most recent versions of SASS - see this thread, for example, and this post too. The upshot is, users either have to hold back from updating SASS, or fix the syntax errors in the .scss files directly. I've been opting for the second option, but it's getting annoying to keep applying the same patches every time I upgrade ExtJS. Is there any hope for this to be fixed in 4.1? It's not been fixed in the preview, to my knowledge, and I couldn't spot it in the list of active bugs still to be addressed.

    For reference, the syntax errors are:
    • mixins/_frame.scss:115 - Defining a function within a mixin is not allowed. The "@function pad" should be moved to the top of the document, outside the x-frame mixin.
    • widgets/_tabbar.scss:31 - Nested mixins are not allowed. The "@mixin tab-bar-top" and "@mixin tab-bar-bottom" should be moved to the top of the document, outside the extjs-tabbar mixin.

  2. #2
    Ext JS Premium Member burnnat's Avatar
    Join Date
    Jun 2011
    Posts
    414
    Vote Rating
    60
    burnnat is a jewel in the rough burnnat is a jewel in the rough burnnat is a jewel in the rough burnnat is a jewel in the rough

      0  

    Default


    Also, the ExtJS theming guide says this under the "Directory Structure" section:
    Due to a bug in Ext JS 4.0.2a you will also need to edit line 62 of appname/extjs/resources/themes/lib/utils.rb from this:
    Code:
    images_path = File.join($ext_path, 'resources', 'themes', 'images', theme)
    to this:
    Code:
     images_path = relative_path
    This ensures images will be served from appname/resources/images rather than appname/extjs/resources/images
    This "bug in ExtJS 4.0.2a" is still around, as far as I know, and is another one of those modifications I make every upgrade. Would be nice to have that one also taken care of in 4.1 if possible...

  3. #3
    Ext JS Premium Member burnnat's Avatar
    Join Date
    Jun 2011
    Posts
    414
    Vote Rating
    60
    burnnat is a jewel in the rough burnnat is a jewel in the rough burnnat is a jewel in the rough burnnat is a jewel in the rough

      0  

    Default


    No word on this? Official bug report with template filed here in the hopes of garnering some attention.