Bug 241 – Annoying to revalidate with textarea

NOTE: The current preferred location for bug reports is the GitHub issue tracker.

Bug 241 - Annoying to revalidate with textarea


Summary:	Annoying to revalidate with textarea

Status:	RESOLVED FIXED

Product:	Validator.nu
Classification:	Unclassified
Component:	Browser-based UI
Version:	HEAD
Hardware:	All All

Importance:	P2 enhancement
Assigned To:	Henri Sivonen

URL:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2008-06-03 21:43 CEST by Simon Pieters
Modified:	2008-09-01 22:51 CEST (History)
CC List:	0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Simon Pieters 2008-06-03 21:43:10 CEST

When validating using the textarea interface, the textarea is replaced with the address field after submitting the form. This is annoying.

It would be nicer if the textarea and file upload interfaces would use XHR instead of normal submit. Or submit to a seamless iframe... :-) Or the results page remembers which input method was used and updates the interface accordingly.

Comment 1 Henri Sivonen 2008-06-04 09:27:48 CEST

(In reply to comment #0)
> When validating using the textarea interface, the textarea is replaced with the
> address field after submitting the form. This is annoying.

Agreed.

> It would be nicer if the textarea and file upload interfaces would use XHR
> instead of normal submit. Or submit to a seamless iframe... :-) 

I agree this would be nice, but I think I'm not going to focus on this feature just yet.

I was hoping that XHR+AC would have allowed a third party to create that UI, but then deployment got postponed.

> Or the results
> page remembers which input method was used and updates the interface
> accordingly.

I guess I'm going to do this. Is there any way to persist a scripting flag across page load without round-tripping a marker via the server?

Comment 2 Simon Pieters 2008-06-04 12:13:46 CEST

(In reply to comment #1)
> Is there any way to persist a scripting flag
> across page load without round-tripping a marker via the server?

Not that I know of. However the script knows if the page was POSTed by looking at the URL. If there's no query string and you're on the "results" page (and show source is enabled), show the textarea.