Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8857447
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 14, 20262026-06-14T14:35:31+00:00 2026-06-14T14:35:31+00:00

I am working on an ExtJS4 application – custom reporting application. ExtJS4 uses terrible

  • 0

I am working on an ExtJS4 application – custom reporting application.

ExtJS4 uses terrible graceful degradation principles by automatically falling back all css3 with images and tables (modified markup). Because of this it horribly bloats the already bloated markup and changes all of the gradients / borders with default images.

I am not sure what else it changes besides css3 elements, but here are the app screenshots.

This is IE8:
Bad - IE8

This is Google Chrome:
Good - Chrome

…

  1. Besides having to inspect all of the markup and undoing these terrible design decisions
  2. Besides having to recreate all of their images to match the existing design
  3. Besides having to modify the core files to force graceful degradation NOT to happen for browsers that do not support x-nlg, x-nbr, etc.

Update 2012-11-23

Sencha slice:
Bad - IE8

ExtJS Core Override:
Good - IE8

Are there any other ways or settings, javascript or sass, to handle all of these compatibility issues more easily?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-14T14:35:32+00:00Added an answer on June 14, 2026 at 2:35 pm

    So with no avail for an answer I will supply the implementation I took.

    As you can see above, this complex ExtJS 4.1 application has a complex design. The sencha slice tool did not work whatsoever (It does work however if you want to keep the all sencha defaults and just change the application’s base color, possibly base SASS variables?).

    On the other hand, you can see how beautiful the Ext overrides turned out. A pretty solid transition and looks 95% the same (or as Chris Coyier would say, “meh, good enough”).

    Below is my implementation:

    Ext.application({
        ...
        init: function () {
            // Override CSS3BorderRadius value which caused render problems in <IE9 when false.
            Ext.supports['CSS3BorderRadius'] = true;
    
            // Hack-ish remove class sniffers from Ext.EventManager (which attaches modrnizer type classes onto the body)
            Ext.getBody().removeCls('x-nbr x-nlg');
        }
        ...
    });
    

    This implementation is elegant in that:

    1. “I” will write cross browser CSS that will work. I do not need sencha to override my CSS with its “smarter”, more terrible, CSS.
    2. I understand legacy browsers cannot handle rounded corners — I don’t want them.
    3. I understand that IE cannot handle linear gradients — I do not want images by default. I want to use filter:progid.
    4. I DO NOT WANT SENCHA TO BLOAT MY MARKUP WITH DOZENS OF CUSTOM IMAGES, DOZENS OF NESTED CONTAINERS, AND TABLES GALORE

    gg hope this helps someone

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have developed a web application using ExtJs4.0.7. The application is working fine in
I'm working on a 100% ExtJS application; the browser downloads all the JavaScript and
Im working on an application in extJS4 and i need to enter 2 values:
Working with Reporting Services 2008 r2. So here's my issue: We have 5 reports
We are using treepanel in our application. It is working fine. But if we
I'm working with ExtJS4 and trying to build a search feature using a form.
I am working on extjs4, my case is: Extjs mvc is used to build
I am working on a relatively large ExtJS MVC application with around >40 Controllers,
Right now, I’m working on a legacy web application that is made up of
I'm new to Extjs4.In Extjs4 loader not working when i use loader: new Ext.tree.TreeLoader()

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.