To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.publish.htmlOpen lugnet.publish.html in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Publishing / HTML / 308
307  |  309
Subject: 
Re: Disabling HTML form button if any changes made to an edit box?
Newsgroups: 
lugnet.publish.html
Date: 
Mon, 2 Jun 2003 23:03:23 GMT
Viewed: 
2548 times
  
In lugnet.publish.html, Dan Boger wrote:
The problem is, that if you have two buttons, one says "Post" and one says
"Preview", people would assume they're in the same form.

I agree with Dan...especially in light of how it's always been (a single form).

PS.  Is the really bad wrapping in the quoted text a result of the new
formatting features?

I'm not sure.  Can you point me to specific examples of "bad wrapping in the
quoted text"?

One thing that I am aware of, however, is a -lack- of wrapping long quoted
lines in one particular circumstance:  Apparently MSIE 6 for Win98 (and possibly
other browsers) takes quoted text and re-line wraps it horribly and into one
long line if you do something within the quoted text that causes a word to wrap.
A reformatted long paragraph is submitted as a single line because WRAP=SOFT is
specified in the <TEXTAREA> tag, and MSIE has no way of knowing that you're
editing a message quoted with ">" characters.

Why WRAP=SOFT instead of WRAP=HARD?

In the beginning, the <TEXTAREA> tag specified WRAP=HARD.  In October of 2000 it
was discovered, however, that MSIE took this a bit too literally and massacred
URLs longer than the width of the window.  So the form was changed
to use WRAP=SOFT for MSIE and WRAP=HARD for all other browsers, and code was
added to automatically break any long lines received.  Since WRAP=SOFT had never
caused any problems, I enabled it for all browsers on May 27, 2003
(just last week).  (Note that changed behavior for non-MSIE browsers, but
kept the behavior the same for MSIE.)

In theory, WRAP=SOFT should work better if not as good as WRAP=HARD, provided
that the server breaks long lines when it receives them.

The problem as I understand it today is that some long lines beginning with
">" are sneaking through.  The wrapping semantics haven't changed much at
all, and in particular the semantics of lines beginning with ">" haven't
changed at all:  Lines beginning with ">" never get wrapped, period.

But perhaps they should -- in the case of excessively long lines (like 120+
characters long), and especially in the case where the line is obviously a
massacred jumble of quoted material with ">" characters appearing every 70
or so character positions.

Any chance that'll be fixed?

Ya.

--Todd



Message has 1 Reply:
  Re: Disabling HTML form button if any changes made to an edit box?
 
(...) Well, I assumed it was already 2 forms until I looked at the actual HTML. To me the horizontal rule between the 2 sections delineated the forms. If others assert they would be confused by 2 forms in this fashion what can I say? Perhaps there (...) (21 years ago, 3-Jun-03, to lugnet.publish.html)

Message is in Reply To:
  Re: Disabling HTML form button if any changes made to an edit box?
 
Quoting "Brian H. Nielsen" <70401.2635@compuserve.com>: (...) The problem is, that if you have two buttons, one says "Post" and one says "Preview", people would assume they're in the same form. I know I will. You can put multiple forms on the same (...) (21 years ago, 2-Jun-03, to lugnet.publish.html)

19 Messages in This Thread:





Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact

This Message and its Replies on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR