Re: [WSG] generated source
On Wed, Feb 27, 2008 at 6:00 AM, Michael MD [EMAIL PROTECTED] wrote: I like the view generated source in the Web Developer Firefox plugin, Firebug is very handy too For html it will display as HTML (without closing slashes) as that is how Firefox interprets things sent as text/html. The .xhtml technique is new to me, although it makes sense considering the difference for application/xml docs. btw does anyone know how to get Firefox 2 plugins to work in Firefox 3 beta? for some reason I can't seem to use both at the same time on the same machine.. You need to make sure you're using different profiles for each, otherwise it will keep trying to update the same profile. For most users this makes sense, but for techies testing Firefox, make sure you run different profiles for each. (The technique under Running Multiple Firefox installs still works: http://alastairc.ac/2006/07/firefox-2-beta-released/ ) Cheers, -Alastair *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
[WSG] generated source
Does anyone have a preferred way to view and validate generated source code? By generated source I mean after Ajax, JavaScript, and so on have done their magic. I'm asking because I'm working on a web application for browsing network devices (close to 9000 routers, switches, WAPs, etc.) that relies on JavaScript (some homemade JS, jQuery, Ajax and JSON) to build virtually all the XHTML. Yet, when I view source via the debug inspect element feature in the latest release of Safari or using Pederick's web developer Firefox add-on, closed tags become unclosed. For example: meta http-equiv=Content-Type content=text/html; charset=UTF-8 / Becomes: meta http-equiv=Content-Type content=text/html; charset=UTF-8 Yet viewing generated source in Firebug, that same meta tag remains closed. Firebug, however, doesn't have (or I haven't noticed?) a way to copy and paste source code for direct input validation to the W3C validator. This, then, is the ultimate goal: to get the generated source, copy it and paste it into a validator. I validated with static mockups prior to de-building the XHTML and giving it over to JavaScript, but I want to validate now to make sure I'm staying on track. Have others run into this problem? Thanks in advance, Jody -- Jody Tate Web Developer - UW Network Systems http://staff.washington.edu/jtate/ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
RE: [WSG] generated source
Hi Jody, I recall having a similar problem. The issue came down (from memory) to the doctype I was using. I was closing elements in xhtml style, while the doctype I was using was html. Firefox was happily removing the extraneous closing elements in the rendered source to fit the doctype. :) Paul *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] generated source
Thanks, Paul, for the suggestion. Doctype, I don't think, is the issue. The doctype is set in the static XHTML that the Ajax builds on as XHTML strict. However, most generated source views remove the doctype, a phenomenon I asked about here: http://ask.metafilter.com/84314/Where-does-the-DTD-go . The W3C validator lets you re-declare a doctype if one is missing, http://validator.w3.org/#validate_by_input+with_options , but even using that option, many of my tags are still already unclosed from the generated source view. -jody On Feb 26, 2008, at 11:37 AM, Paul Bennett wrote: Hi Jody, I recall having a similar problem. The issue came down (from memory) to the doctype I was using. I was closing elements in xhtml style, while the doctype I was using was html. Firefox was happily removing the extraneous closing elements in the rendered source to fit the doctype. :) Paul *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] generated source
There are a few plugins for firefox that does validation for you. Can't remember the names of them offhand though. Sorry. On Wed, Feb 27, 2008 at 4:44 AM, jody tate [EMAIL PROTECTED] wrote: Does anyone have a preferred way to view and validate generated source code? By generated source I mean after Ajax, JavaScript, and so on have done their magic. I'm asking because I'm working on a web application for browsing network devices (close to 9000 routers, switches, WAPs, etc.) that relies on JavaScript (some homemade JS, jQuery, Ajax and JSON) to build virtually all the XHTML. Yet, when I view source via the debug inspect element feature in the latest release of Safari or using Pederick's web developer Firefox add-on, closed tags become unclosed. For example: meta http-equiv=Content-Type content=text/html; charset=UTF-8 / Becomes: meta http-equiv=Content-Type content=text/html; charset=UTF-8 Yet viewing generated source in Firebug, that same meta tag remains closed. Firebug, however, doesn't have (or I haven't noticed?) a way to copy and paste source code for direct input validation to the W3C validator. This, then, is the ultimate goal: to get the generated source, copy it and paste it into a validator. I validated with static mockups prior to de-building the XHTML and giving it over to JavaScript, but I want to validate now to make sure I'm staying on track. Have others run into this problem? Thanks in advance, Jody -- Jody Tate Web Developer - UW Network Systems http://staff.washington.edu/jtate/ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** -- - http://myfitness.ning.com A community of people that care about their health and fitness Free fitness videos, recipes, blogs, photos etc. -- *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] generated source
On Tue, 26 Feb 2008 10:44:13 -0800, jody tate wrote: Does anyone have a preferred way to view and validate generated source code? By generated source I mean after Ajax, JavaScript, and so on have done their magic. [...] Yet viewing generated source in Firebug, that same meta tag remains closed. Firebug, however, doesn't have (or I haven't noticed?) a way to copy and paste source code for direct input validation to the W3C validator. This, then, is the ultimate goal: to get the generated source, copy it and paste it into a validator. I validated with static mockups prior to de-building the XHTML and giving it over to JavaScript, but I want to validate now to make sure I'm staying on track. Have others run into this problem? Yes. I have come across it, although for me it is not a problem. This behavior seems logical to me. After all, what displays is the browser's interpretation of the document, which is likely HTML. Unless you are doing something server-side, you are likely sending the documents to the browser with an HTML MIME type, as opposed to XHTML, which requires special handling. One suggestion I have to get Firefox to treat the page as XHTML is to rename your document with dot-xhtml (.xhtml) extension instead of the dot-htm or dot-html. This works from the hard drive, and quite a few hosts are set up to send the correct MIME type as well. Not all are though - you need to check with your host. You may have problems viewing this in Internet Explorer, so don't use it as a permanent web page - just use it for your purpose of validating generated code. I hope this suggestion helps. [Aside] I help out at a computer lab where web design is taught. One misconception I see over and over is that putting things like an XHTML DOCYPE or declaring UTF-8 encoding in a META element somehow alters the document itself. Saying it is so does not make it so, despite what certain politicians would have us believe. Cordially, David -- *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] generated source
Does anyone have a preferred way to view and validate generated source code? By generated source I mean after Ajax, JavaScript, and so on have done their magic. I like the view generated source in the Web Developer Firefox plugin, Firebug is very handy too btw does anyone know how to get Firefox 2 plugins to work in Firefox 3 beta? for some reason I can't seem to use both at the same time on the same machine... (I hope Firefox isn't going down the IE route of only letting you use one version at a time!) *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
