[thelist] RE: [ - Examples of Importing XML into Netscape or Mozilla? - ]

.jeff jeff at members.evolt.org
Wed May 22 19:15:01 CDT 2002


peter,

><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> From: Peter Thoenen
>
> We are not here to discuss bugs [...]
><><><><><><><><><><><><><><><><><><><><><><><><><><><><><

oh?  surely these bugs hamper the ability to develop proper web-based
applications, no?

><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> (try in 100% css1 complaint IE 6 using a xhtml1.1
> doctype <input type="checkbox" style="border: 1px solid
> #000000" name="" value=""/> and tell me what you get..
> 100% css1 complaint huh)
><><><><><><><><><><><><><><><><><><><><><><><><><><><><><

which xhtml1.1 doctype?  transitional?  strict?

btw, you forget a name attribute value.

you also forgot to leave a space between the closing double-quote of the
value attribute and the closing slash in your <input> tag.

oh, you also forgot to wrap that input in a <form></form> block?

what's the full 100% css1 test document look like that you're saying i
should try?

><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> ... we are talking about how Mozilla hampers web
> development (with applications).
><><><><><><><><><><><><><><><><><><><><><><><><><><><><><

and believe it or not, bugs play a huge role in that.

><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> I can't think of a single web application in my life I
> have developed or even seen that I needed THE CLIENT
> (or end user) to print the source to a form submitted
> to itself.
><><><><><><><><><><><><><><><><><><><><><><><><><><><><><

he didn't say print the source.  he said *view* the source and *print* the
page in separate sentences.

   The "view source" will do a 'get' again on the URL,
   resulting in the source you're looking at being
   different from what the browser rendered.

from a development view, that's a significant problem?  as a developer, when
i view the source i *expect* it will look exactly as the browser got it from
the server.

he then goes on to describe that printing exhibits the same behavior of
doing a get for the content to be printed rather than printing what's on the
screen.

so, we've got two instances where the end result is the same.  viewing the
source gives you different source.  printing gives you different source
which results in a document that's rendered differently than the document in
the browser window.

that's huge.

><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> Now when you get done complaining about specific Mozilla
> bugs that don't effect web development (as in
> applications) [...]
><><><><><><><><><><><><><><><><><><><><><><><><><><><><><

easy sparky.

><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> ..maybe you can point me to some code that Mozilla can't
> do but is required for your web applications to run (or
> hell..even code that makes you life as a developer more
> difficult).
><><><><><><><><><><><><><><><><><><><><><><><><><><><><><

there's lots.  here's one that i dislike alot that makes my life of
developing web-based applications difficult.

how about mozilla not firing any event when a scrollable region is scrolled.
this makes it impossible to show tabular data in a fixed size box where the
overflow scrolls and have separate header columns above the scrollable
region that move horizontally to match up with columns in the scrollable
region.

.jeff

http://evolt.org/
jeff at members.evolt.org
http://members.evolt.org/jeff/






More information about the thelist mailing list