Comments on: Web Page, Mutated

By: 今日連結 (2005-07-10) [JeffHung.Blog]

今日連結 (2005-07-10) [JeffHung.Blog] — Wed, 02 May 2007 11:50:55 +0000

[...] Web Page, Mutated – 所以說，Mail Archive Format 每次都去重新抓網頁，應該是會產生真的 “Web page, complete” 的囉？ [...]

By: Paul

Paul — Sat, 17 Dec 2005 00:16:58 +0000

2Dimitriy:

Why is that? I’ve used DOM Inspector and can’t see any advantages…

By: Dmitriy

Dmitriy — Tue, 13 Dec 2005 07:00:47 +0000

DOM inpector can be better

By: Jason

Jason — Thu, 25 Aug 2005 20:08:19 +0000

Just a thought I had and didn’t see in any of the comments but why not send the webpage you are trying to view the css code on through the css validator at http://www.w3.org?

By: /T

/T — Mon, 11 Jul 2005 11:07:01 +0000

Klaus, you can consider yourself lucky if you get the error message. I have seen cases where doing a “Save Webpage, complete” on a page that has a link rel to a style sheet in which another CSS is imported via @import sends IE/Win into a death spiral.

By: Klaus Hartl

Klaus Hartl — Sun, 10 Jul 2005 19:55:19 +0000

If you use external style sheets with @import, this breaks the whole "Save Webpage, complete" thing in IE/Win. IE stops with a message like "Could not save web page". Ugh!

By: JeffHung.Blog » 今日連結 (2005-07-10)

JeffHung.Blog » 今日連結 (2005-07-10) — Sun, 10 Jul 2005 14:38:44 +0000

[...] 還不如說誠實和負責，我覺得那才是blogger的信任來源。 Web Page, Mutated – 所以說，Mail Archive Format 每次都去重新抓網頁， [...]

By: Lachlan Hunt

Lachlan Hunt — Sat, 09 Jul 2005 10:06:36 +0000

Browser’s have long been know to mangle the content of documents with any attempt to save the complete web page, including Mozilla. It’s not uncommon that saving a perfectly valid web page (particularly an XHTML document served as text/html) will not remain either valid or well formed. Although i wasn’t aware of IE mangling the stylesheet too, I never rely on any form of “save as web page, complete” in any browser.

By: Ethan

Ethan — Thu, 07 Jul 2005 22:09:35 +0000

Ack. Eric, you're right, of course---thanks for clarifying. Ethan no speak good caffeine without.

By: Dave S.

Dave S. — Thu, 07 Jul 2005 20:29:56 +0000

You wouldn’t believe (or would you?) the number of Zen Garden submissions I get which have started their life as saved source from Win/IE. THE ALL CAPS HTML KIND OF GIVES IT AWAY, PEOPLE.

From a CSS perspective, none of them seem to have suffered for this since they appear to render properly. Which I continually find surprising.

Oh, and while I’m here… make that a second vote for Xylescope. Totally worth the $15.

By: Feaverish

Feaverish — Thu, 07 Jul 2005 18:33:23 +0000

Tangentially related, I've lately been using a great inspector called Xylescope, which breaks down the CSS and HTML and uses WebKit to display pages.

By: Eric Meyer

Eric Meyer — Thu, 07 Jul 2005 18:01:13 +0000

Hm, perhaps you're right, Sebastian:

It should just present the style rules as they appear in the style sheet itself. Nothing more, nothing less. Splitting properties is of no use. There already is the “Computed Style” section of the node properties. Use this one if you care for the split properties.

...although I would still want a preference to show or suppress the split/computed/whatever rules in the CSS Style Rules view, as long as they were differently presented. Being able to see both declared and computed styles in one place would be more useful (to me, anyway) than splitting them into two entirely separate views. Ethan: I suspect Firefox was actually wrapping all the rows of each of your tables in a tbody element, not wrapping a bunch of tables in one tbody element. Correct?

By: Ethan

Ethan — Thu, 07 Jul 2005 16:33:34 +0000

I've been bitten by this before; Firefox decided that it wanted to wrap some tables in a tbody element, which did wonders for a.) breaking some child selectors I'd been writing and b.) making me tear my hair out by the fistfuls. Huzzah for browsers. They're the best.

By: dolphinling

dolphinling — Thu, 07 Jul 2005 16:18:30 +0000

I completely agree with Steve Fulton: the DOM Inspector should (and does) show what the browser is doing, not what was originally said. After all, it would be pretty useless if it showed you the exact same thing as "view source", wouldn't it? @mike: I'm not sure exactly what you mean, but html by definition has capital letters for tag names in the DOM and various other rules that you're probably seeing. It's entirely likely that IE and maybe gecko have bugs, though.

By: mike

mike — Thu, 07 Jul 2005 14:10:17 +0000

this is also what you have to deal with when using visual editing mode on either browser. Regardless of the CSS (or HTML for that matter) you put into a visual editing input field in IE, you’ll get the split-apart shortcut rules, capital letters, etc etc. mozilla does it too, of course, just not quite as blantantly. fun stuff.