Find by ID:
Go
[Log in | Register]
Home
Support Center Home
Categories (Beta)
Report Issue
Report a Bug
Make a Suggestion
Ask a Question
Security
Log in
Register
Forgot Password
Support Center Stats

Issue Reports
Total: 57,085
Active: 474
Processed: 56,611

Suggestions
Total: 21,935
Active: 102
Processed: 21,833

Questions
Total: 134,411
Active: 186
Processed: 134,225

1,994 Knowledge Base Articles

1,742 Code Central Examples

Powered by Developer Express AJAX-Enabled ASP.NET components

This website is powered by Developer Express ASP.NET technologies including the ASPxMenu, ASPxNavBar, ASPxTabControl, ASPxSiteMapControl, ASPxPopupControl and the ASPxGridView and Editors Suite.
Database connectivity is via eXpressPersistent Objects.

View Issue

Bug Report Details: ASPxGridView styles got lost after callback

ID: Q201136
Problem Type: Bug Report
Opened By: alex satava
Reviewed by DevExpress: Yes
Status:
Processed
Resolution:
By Design
Modified On: 4/9/2009 8:07:21 AM
Reproduced:
Yes
Product Group: .NET
Product: ASPxGridView and Editors Suite
Version: 8.3.3
Fixed In Release: n/a
Operating System: Windows XP
IDE: Microsoft Visual Studio 2008
Categories: n/a
Log in to Track Changes or Edit
Description
Discussion (beta)

Created by alex satava at 4/3/2009 8:33:42 AM
Attachment: screen.zip (30096 bytes)

hello

i am using a aspxgridview in a aspxpopupcontrol (which is dynamically set to the page url
using setcontenturl).

problem: when i trigger a "performcallback" on the gridview to update the datarows, then
the styles on the page are applied with different priorities.

as example, when i look at a page titel label (which is not even part of the gridview), the
applied styles look as follows (using IE6 + IEdevelopertoolbar):

/* Rule 5 of /WebResource.axd?d=YqryKbmtmQzEPccv5RS_J4Z8-P-JInJ_Z1HyOwbEKaX1FuD9u_jvnNsmDEKKxA0S7uBPOOJ-EDT4CQQhL-dcEU7W7BmC32Xiqmg3h9Fp8GcZuCHXJW_GaLC8qV9F_IXyOExN6_EPFKrGaT68IQ11Rw2&t=633676180631250000 */
.dxeBase {     FONT-SIZE: 9pt; FONT-FAMILY: Tahoma}
/* Rule 16 of MasterStyles.css */
.xHDRTXT { FONT-WEIGHT: bold; FONT-SIZE: 16px}
/* Rule 2 of ../Styles/PriceCoach.css */
.dxeBase {     FONT-FAMILY: Verdana}

now, before performing the callback, the label appears as verdana 16px bold,
thus using parts of all three style sources (devexpress webresource.axd,
my masterstyles.css and my custom pricecoach.css).
> see attached b4callback.jpg

after the callback, the label appears as tahoma 9pt bold, thus applying the
same styles (e.g. bold is taken from masterstyles.css), but setting a higher
priority on the devexpress webresource.axd, thus overriding my font size and
font family definitions.
> see attached aftercallback.jpg

this happens to all controls on the page, including my custom styling for the
grid template controls...

how can this be resolved?

regards,
alex satava
xss ag

after performing the callback

/* Rule 5 of /WebResource.axd?d=YqryKbmtmQzEPccv5RS_J4Z8-P-JInJ_Z1HyOwbEKaX1FuD9u_jvnNsmDEKKxA0S7uBPOOJ-EDT4CQQhL-dcEU7W7BmC32Xiqmg3h9Fp8GcZuCHXJW_GaLC8qV9F_IXyOExN6_EPFKrGaT68IQ11Rw2&t=633676180631250000 */ .dxeBase {     FONT-SIZE: 9pt;     FONT-FAMILY: Tahoma} /* Rule 16 of MasterStyles.css */ .xHDRTXT {     FONT-WEIGHT: bold;     FONT-SIZE: 16px} /* Rule 2 of ../Styles/PriceCoach.css */ .dxeBase {     FONT-FAMILY: Verdana}

Processed (Insufficient Information) by DevExpress Team at 4/3/2009 12:11:00 PM

Hi Alex,

Unfortunately, the information you provided doesn't allow me to clearly diagnose this problem.
If possible, post a complete sample project showing the issue. Then, I'll check for a solution.

Thanks,
Alex

Reactivated by alex satava at 4/3/2009 3:49:54 PM
Attachment: dxIssue.zip (41051 bytes)

hello alex

i have stripped down the page to a sample of the bug.

when you start the project, note the styles of the different controls.
then press the "callback" button, and note how the styles of the controls
change. the only thing the callback button does, is perform a callback on
the gridview. however the styles of all controls seem to be applied in a
different order than on the original page load. a page refresh brings back
the correct styles.

ps. i use three css, one for the page specific sizes of standard controls,
one master for all controls and one for theming of colors and fonts.

thanks for looking into this, i have no clue how to fix this.

regards,
alex satava
xss ag

Updated by DevExpress Team at 4/6/2009 2:13:17 PM

Hi Alex,

Thanks for posting your files. I see the problem. Apparently, this is an actual ASPxGridView issue.
However, I'm afraid we need some additional time to classify this misbehavior.
I'll update this thread once we have any results. Please accept our sincere apologies for the inconvenience.

Thanks,
Alex

Reproduced by DevExpress Team at 4/6/2009 2:13:38 PM

Processed (By Design) by DevExpress Team at 4/7/2009 12:25:24 PM

Reactivated by alex satava at 4/8/2009 5:20:41 PM

hello alex

thanks for your information. i understand, that themes might solve the issue.
however our application is not designed to use different themes in regards to
the fonts used. this is something that should be driven by a dynamically added
stylesheet. i wish to explicitly leave the font-family definition customizable.

i don't understand why a css class such as ".dxebase .xHDCCTX" is overridden
by a class ".dxebase" which is delivered by the webresource after callback!

if this is by design, then devexpress aspx components are explicitly not designed
to have fonts and font-sizes configured outside of themes, which is a major
drawback for us and will make us rethink the use of these components in
future applications, and even in the current application in development.

questions:

1) what is the "performance cost" of using themes instead of CSS, both on server-side and client-side?

2) how "safe" is the use of the !important definition in CSS? is this supported by all browsers?

thanks for your feedback...

regards, alex

Processed (By Design) by DevExpress Team at 4/9/2009 8:07:21 AM

Hi Alex,

Thanks for the response.
Generally, themes (skins) are designed to make the mechanism of modifying an application style easier, and there's some additional server processing performed to apply skin attributes to page controls before rendering them. For reference, check this MSDN article: ASP.NET Themes and Skins Overview.
To learn about CSS support in major web browsers, refer to the web browser standards support document.

Thanks,
Alex