|
|
Rank: Advanced Member
Groups: Member
Joined: 11/13/2008
Posts: 43
|
Hi, The Dialog control seems to render non-XHTML-compatible markup. Specifically, it outputs a tag of 'collspacing' instead of 'cellspacing' (first reported in August 2007), inserts a <style /> tag in an invalid location, and does not include alt tags for its images. You can see an example of this here: http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fwww.markrae.net%2Fwelcome.aspxIs there a workaround for this? Regards, Mark Rae N.B. I would be grateful if you would please not edit or delete this post, as you have done with some of my previous posts - thanks.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,194
|
Hi,
We will look into the issue and let you know what we find.
As to editing and deleting post, unfortunately we will continue to do so when we see fit. It is important for you to understand that the forum is managed by us and it is meant to be a useful resource for all of our users. We put technical questions online so that many users can search the forum and see whether other users are having similar issues, whether an issue has been resolved, etc.
Specifically, the forum is not a place for you to vent your complain (use “Contact Us” page if you have any complain with our product or service in general, such as support policy), or exercise your right to freedom of speech, or to demonstrate how smart you are, or whatever other purpose you want it to be. Simply put, the forum is our property, and when we see thing that we deemed inappropriate, we clean it up.
You are welcome to continue post technical questions or issues about the product in the forum and we will try our best to address them. (We do not offer any guarantee though, mostly because a lot of times some users wanted this way and some other users wanted it that way and it is simply not possible to satisfy them all). If you believe you can use the forum for other purposes, such as showing how good you are with spellings, you will need to find somewhere else to do that.
Please keep in mind that we have no intention to upset you. We value you as a customer by trying to provide the best product and service possible and we expect this to be done in a mutually friendly and respectful manner because it is the best interest of both of us to keep it that way. We will be very grateful if you agree on that.
Hope this clarifies our position.
Thanks
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,194
|
Hi, We have posted a new build that addressed this issue. Please see your private message for download location. In order for the output to be XHTML-compatible, you may need to add the following line into your head section:
Code: HTML/ASPX
<eo:Head runat="server"></eo:Head>
This is not needed if you do not have any server side rendering code in the head section. However if you have any rendering block ('<%= =>') such as:
Code: JavaScript
var objDialog = eo_GetObject('<%=dlgReview.ClientID%>');
In your head section, you can either move that into body section, or add eo:Head element. Thanks
|
|
Rank: Advanced Member
Groups: Member
Joined: 11/13/2008
Posts: 43
|
eo_support wrote:Hi, We have posted a new build that addressed this issue. Please see your private message for download location. In order for the output to be XHTML-compatible, you may need to add the following line into your head section:
Code: HTML/ASPX
<eo:Head runat="server"></eo:Head>
This is not needed if you do not have any server side rendering code in the head section. However if you have any rendering block ('<%= =>') such as:
Code: JavaScript
var objDialog = eo_GetObject('<%=dlgReview.ClientID%>');
In your head section, you can either move that into body section, or add eo:Head element. Thanks - that certainly seems to have fixed the XHTML validation issues: http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fwww.markrae.net%2Fwelcome.aspxI saw the eo:Header stuff in the helpfile, but as it said it was for ASP.NET 1.1 only, I didn't bother trying it...
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,194
|
Thanks for the update. The document is not entirely accurate in this case and we will try to correct it as soon as possible. eo:Head is generally not needed for ASP.NET 2.0, but having server side rendering code in the head section is an exception.
|
|
Rank: Advanced Member
Groups: Member
Joined: 11/13/2008
Posts: 43
|
Mark Rae wrote:that certainly seems to have fixed the XHTML validation issues However, there now appear to be CSS validation issues, specifically that padding-a, padding-b, padding-c and padding-d don't exist: http://jigsaw.w3.org/css-validator/validator?uri=http%3A%2F%2Fwww.markrae.net%2Fwelcome.aspx
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,194
|
Hi,
Can you check whether those CSS attributes already exist in your .aspx file? Our old versions used to incorrectly generates these values, but that should have already been fixed. However whatever that was generated in your .aspx file will still be there unless being edited again.
Thanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 11/13/2008
Posts: 43
|
eo_support wrote:Can you check whether those CSS attributes already exist in your .aspx file? Yes they do. The reason for this is because I simply copied the dialog from the Dialog\Designs\Windows Vista\Demo.ascx file in your sample project...
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,194
|
Ah. That explains! Those were created a while ago with the old version.
Thanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 11/13/2008
Posts: 43
|
eo_support wrote:We have posted a new build that addressed this issue. Please see your private message for download location. In order for the output to be XHTML-compatible, you may need to add the following line into your head section:
Code: HTML/ASPX
<eo:Head runat="server"></eo:Head>
Although (as previously mentioned) this build does indeed now pass XHTML validation, this has caused two additional tooltips to appear. If you hover the mouse over the Dialog header, the tooltip 'hdr' appears, and if you hover the mouse over the close button the tooltip 'close' appears. This is not a major issue since it doesn't affect the Dialog's functionality as such, but it is irritating. Although a <img /> element needs to have an alt tag in order to be XHTML compatible, the alt tag can be empty. Would it be possible to modify the generated markup to replace alt="hdr" with alt="", and also for the other instances e.g. alt="close", alt="+", alt="|" etc? Or, even better, provide additional properties e.g. HeaderToolTip and CloseButtonToolTip which developers could set to an empty string...
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,194
|
Hi,
That seems to make perfect sense. We will see what we can do.
Thanks!
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,194
|
This issue is fixed in build 2008.0.54.
|
|