Showing posts with label xhtml. Show all posts
Showing posts with label xhtml. Show all posts

Wednesday, March 21, 2012

XHTML 1.1 Firefox and Opera problem

I installed AJAX Beta2 and used the CTP template to create a new web site. Which creates default.aspx page, with the doc type of:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
I have a table with images. I run the page in IE7 looks perfect. I ran in FF and Opera the cells height are 5 to 10 px to big. After pulling my hair for about 2 hours. I notice the doctype.
I set it to this: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
And the table is correct (works in IE as well).
Should an AJAX site doctype be XHTML 1.1? Does it matter? Why did this break firefox on something so simple as a table?
Thanks
Rick 
AJAX should support site doctype XHTML 1.1 in the release version. I aslo find the similar issue to yours.The Ajax control size?is?somewhat?different?
in?different?browers?such?as?IE,FireFox,Opera,Safari.

Ajax, shorthand for Asynchronous JavaScript and XML, is a web development technique for creating interactive web applications. The intent is to make web pages feel more responsive by exchanging small amounts of data with the server behind the scenes, so that the entire web page does not have to be reloaded each time the user makes a change. This is meant to increase the web page's interactivity, speed, and usability.
The Ajax technique uses a combination of:
XHTML (or HTML) and CSS, for marking up and styling information.
The DOM accessed with a client-side scripting language, especially ECMAScript implementations such as JavaScript and JScript, to dynamically display and interact with the information presented.
The XMLHttpRequest object is used to exchange data asynchronously with the web server. In some Ajax frameworks and in certain situations, an IFrame object is used instead of the XMLHttpRequest object to exchange data with the web server, and in other implementations, dynamically added <script> tags may be used.
XML is sometimes used as the format for transferring data between the server and client, although any format will work, including preformatted HTML, plain text, JSON and even EBML. These files may be created dynamically by some form of server-side scripting.

XHTML 1.1 validation and Atlas

Hello all,

Previously, I tried Atlas but abandoned it when it failed to produce valid XHTML 1.1 according to the W3C validator. The problem was that it did not recognize the tags inside the <script type="text/xml-script"> blocks, or the xmlns:script attribute.

Now, after surveying many other frameworks and finding them either lacking for my purposes or unable to run in a partial-trust environment, I'm turning back to see if Atlas can be made to work. Two questions:

    Has anyone come up with a workaround for the invalid XHTML?Is the XHTML really invalid, or is the W3C validator lying? (Please substantiate your claim if it's the latter.)
No ideas?
I need to know about this aswell if anyone can help?

XML namespaces and XHTML are a bit tricky. There are other Ajax toolkits wrangling with the same issue. It has to do with a lot of things, but is not unique to Atlas.

If you are interested, you can read some interesting information on XHTML and other namespaces athttp://www.w3.org/TR/xhtml1/normative.html.

http://www-128.ibm.com/developerworks/xml/library/x-namcar.html

And, for this topic in particular, see item 3 here

http://codinginparadise.org/weblog/2005/08/xhtml-considered-harmful.html

And, a possible solution, referenced via the previous (albeit circuitiously), create a custom DTD!http://www.alistapart.com/articles/customdtd/

How quaint. I thought DTD was deprecated by XML Schema... And, so we are to use a deprecated syntax to make XHTML (the future of HTML) work. Not only that, how is using a custom DTD compliant with XHTML anyway? Ah, well. I don't have any answers.

Sorry for the messy response. It's a messy problem.


Thanks very much for the info.

XHTML Validation

Pages that previously validated as XHTML no longer do after adding the DropShadowExtender. The validator is complaining about undeclared elements such as "behaviors" in the output from the Atlas controls.

Any solution to this?

Mike Hanson

Is it just the DropShadow extender, or is it the addition of any extender? I suspect it's the latter and that it's due to the XML Script that Atlas adds. If so, this question may be better posed in one of the Atlas forums?

Thanks for the response David.

I have had a look at the source that was validated and you are correct, all of the errors point to the xml-script section appended to the end of the document, so I will go look through the Atlas forums to see if anyone else has raised the issue, if not I will post my original question there.

Thanks again
Mike Hanson