 | | Re: Disabling HTML form button if any changes made to an edit box?
|
|
(...) I think that might make more work for the user than is strictly necessary. If the server detects changes automatically (or if JS disabled the "Post" button automatically), then it eliminates a step. --Todd (21 years ago, 2-Jun-03, to lugnet.publish.html)
|
| |
| | Re: Disabling HTML form button if any changes made to an edit box?
|
|
(...) Todd, I was justing post a blog when i thought of something (well, saw how the blog did it) - one the page where you compose the text, it has one button that says "preview". when you hit it, you go to a page with the text, but you are unable (...) (21 years ago, 2-Jun-03, to lugnet.publish.html)
|
| |
| | 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)
|
| |
| | Re: Disabling HTML form button if any changes made to an edit box?
|
|
(...) People already deal with multiple forms on a page and are used to the fact that the button they click is relevant only for the data on that form. The current Message Preview page is layed out in a manner that clearly suggests it is 2 different (...) (21 years ago, 2-Jun-03, to lugnet.publish.html)
|
| |
| | Re: Disabling HTML form button if any changes made to an edit box?
|
|
(...) That part sounds great to me. (...) And this part also sounds great -- except for one thing: What if someone makes edits in the lower form, but then clicks the "Post" button in the top form? --Todd (21 years ago, 2-Jun-03, to lugnet.publish.html)
|
| |
| | Re: Disabling HTML form button if any changes made to an edit box?
|
|
(...) I'll trust you on how other browsers work, you've got to maintain compatability. You can still accomplish forcing a preview before every post by removing the post button from the message edit form, leaving only the preview button. On the (...) (21 years ago, 2-Jun-03, to lugnet.publish.html)
|
| |
| | Re: Announcing FTX for discussion groups
|
|
(...) Do you have Lucida Typewriter? Try setting your fixed-width font to default to that...it's a bit easier on the eyes than Courier. (...) Well, the only consolation I can offer today is a promise that we're making movements towards CSS, which (...) (21 years ago, 2-Jun-03, to lugnet.publish, FTX)
|
| |
| | Re: Announcing FTX for discussion groups
|
|
(...) I guess I don't see the advantage of this part, and I can't stand how when reading via the web it makes the listed posts look one way, and the posts themselves a completely different way. Plus, that fixed-width font is a killer on the eyes. (...) (21 years ago, 2-Jun-03, to lugnet.publish, FTX)
|
| |
| | Re: Disabling HTML form button if any changes made to an edit box?
|
|
(...) I like that idea. In fact I could even implement that immediately without any CRC or JS. That's a great idea, Brian, thanks! The top half would have only a "Post" button (and the "E-mail me a copy" checkbox) and the bottom half would have only (...) (21 years ago, 2-Jun-03, to lugnet.publish.html)
|
| |
| | Re: Disabling HTML form button if any changes made to an edit box?
|
|
(...) Except that relying on the browser's Back button is asking for trouble. Say you edit a reply, look at the preview, then go do something else, and when you return, the page is gone from your browser's cache. That would be a nasty surprise. I've (...) (21 years ago, 2-Jun-03, to lugnet.publish.html)
|
| |
| | Re: taking good photos
|
|
(...) While there is more color fideltiy at higher bit-depths, above a certain point the human eye can't tell the difference. 24-bit is also termed "true color" because it's 16.7 million color range is close to the limit of what the human eye can (...) (21 years ago, 2-Jun-03, to lugnet.space, lugnet.publish.photography)
|
| |
| | Re: Disabling HTML form button if any changes made to an edit box?
|
|
(...) That makes sense. You still don't need the CRC, even if you keep the message edit section on the Message Preview page. In the bottom messge edit section just do the same thing as suggested for the message edit page - combine the post & preview (...) (21 years ago, 2-Jun-03, to lugnet.publish.html)
|
| |
| | Re: Disabling HTML form button if any changes made to an edit box?
|
|
Quoting "Brian H. Nielsen" <70401.2635@compuserve.com>: (...) while that's workable, I like being able to edit while seeing the end result that caused my edit. Meaning if I'm trying to change some formatting, I wouldn't want to have to hit back, to (...) (21 years ago, 2-Jun-03, to lugnet.publish.html)
|
| |
| | Re: Disabling HTML form button if any changes made to an edit box?
|
|
Quoting Todd Lehman <todd@lugnet.com>: (...) I'd think label it "Preview" on the initial submit, then "Preview/Post" in the preview page. JS would be difficult to deal with undone changes, as well as confusing - "There was the post button there, and (...) (21 years ago, 2-Jun-03, to lugnet.publish.html)
|
| |
| | Re: Disabling HTML form button if any changes made to an edit box?
|
|
(...) You don't even need the CRC. Do what you said on the message edit page about combining post & preview so that there is only preview, but then on the Message Preview page remove the whole lower section containing the message edit box, preview (...) (21 years ago, 2-Jun-03, to lugnet.publish.html)
|
| |
| | Re: Disabling HTML form button if any changes made to an edit box?
|
|
(...) Sounds great in theory, and I think the CRC is a great fallback check if JS isn't available, and I like that the CRC method is forgiving of undone changes... But if there were only one button, what would you label it? "Preview or Post"? One (...) (21 years ago, 2-Jun-03, to lugnet.publish.html)
|
| |
| | Re: Disabling HTML form button if any changes made to an edit box?
|
|
(...) why use JS? just combine the post and preview button to one, and detect on the server if the data was changed. If it was, preview, if it wasn't (matches a CRC in a hidden form element), it posts. (21 years ago, 2-Jun-03, to lugnet.publish.html)
|
| |
| | Re: New Gear Boxes and Motor Systems
|
|
Thanks, Todd (...) Actually I didn't noticed I was in FTX mode... BTW, could it be possible to keep a cookie with personnal preference about FTX ? While it can be very useful, I'd prefer to default to plain text for most ordinary messages ! (...) I (...) (21 years ago, 2-Jun-03, to lugnet.technic, lugnet.publish)
|
| |
| | Disabling HTML form button if any changes made to an edit box?
|
|
This must be easy with JavaScript, right?-- I'd like to disable a submit button (turn it gray out and non-clickable) in an HTML form if the user changes any data in an editable text field within the form. The editable text fields are of type <INPUT (...) (21 years ago, 2-Jun-03, to lugnet.publish.html, FTX)
|
| |
| | Re: taking good photos
|
|
(...) I don't think I am. :-) I'm not saying that the end result of a 2x-downsampled 10x digital zoom will look any better in 24-bit color than a native 5x optical zoom would look in 24-bit color. It won't. What I'm saying is that a 2x-downsampled (...) (21 years ago, 2-Jun-03, to lugnet.space, lugnet.publish.photography)
|
