5 Jun 2012 8:02 AM #1
Unanswered: x-body applied even with scopeResetCss = true
I'm trying to upgrade from 4.0.1 to 4.0.7 or 4.1.0. In 4.0.1 using scopeResetCss = true caused ExtJs to not apply x-body to the body tag of my HTML.
When I upgrade this is applied and overrides all the CSS I already have.
Is there anyway to disable this from happening? even ext-all-scoped.css has this issue.
I'm loading ext as follows:
11 Jun 2012 11:04 AM #2
- Join Date
- Jul 2010
- Houston, Tx
- Vote Rating
Try using: extjs/resources/css/ext-all-scoped.css
7 Aug 2012 5:29 PM #3
This worked in 4.0.x
I now want to embed an ExtJS widget in an old website and I get CSS styles screwed up because x-body class gets applied to BODY.
8 Aug 2012 12:56 PM #4
Can anyone confirm the last version of ExtJS in which this actually works as expected?
The earliest version I have is 4.0.4, and it doesn't work. Having that knowledge will help me track down the issue (or explanation).
9 Aug 2012 5:03 AM #5
I've just checked an existing application written on version 4.0.7 where scoped CSS seemingly works, but I still see x-body class applied to BODY. For some lucky reason it did not screw up styles in that particular application which made me think that x-body wasn't there.
That makes me think that there was probably never an ExtJS version where x-classes were not applied to BODY and HTML when using CSS scoping .
9 Aug 2012 6:54 AM #6
As far back as I can see, that looks to be the case.
For some lucky reason it did not screw up styles in that particular application which made me think that x-body wasn't there.
18 Sep 2012 1:30 AM #7
- Join Date
- Dec 2010
- Hamburg, Germany
- Vote Rating
Ran into the same issue today.
The problem hardly causes problems when within a component layout. But we use the scopeResetCss option to be able to create windows and other components on top of an existing website to display movable administrative tools. With x-body applied in some cases (where we do not explicitly set the attributes in the sites styles) the x-body definition with font-family, font-size and color specified break our original site layout.
I guess a working fix would be to move the styles from x-body to x-reset, since x-reset is created around all components anyway.
13 Nov 2012 10:18 AM #8
Sorry to necro the thread but I have the same issue. I'm trying to use ExtJS in an existing page so I don't want x-body or any other classes applied to the <body> tag.
Here's the header code:
<body id="ext-gen1018" class="x-body x-gecko">
2 Dec 2012 4:54 AM #9
7 Feb 2013 10:20 PM #10
Any update on this one?
I agree with the previous post: what does a JS library has to write something in the BODY of the page!?
By default this kind of functionality should be disabled and enabled on request not the other way around.