-
Notifications
You must be signed in to change notification settings - Fork 191
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor how we submit a bug #2288
Comments
(this is a post refactor issue) |
I think so. I was just realizing the way we handle form submit is kinda... wonky. Right now on submit we call So probably |
#2276 (comment) is one idea to explore. |
Changing the title, but we should be sure it also covers error conditions. |
Would be nice to use Promises... or at least jQuery.Deferred. I wonder how painful an upgrade from jQ 1.11.X to 3.X would be (I'm pretty sure we don't try to support IE8 anyways)... |
Also, bump the file upload timeout.
Also, bump the file upload timeout.
And organize some local variables as props on BugForm.
Now we use jQuery Deferreds (Promises/A+ compatible) to handle success and error conditions. If an image passes validation on the server, the issue will be sumitted. If there's a problem, it won't be submitted and the user will have to upload a new image and try again.
…ate. And update their values via JS.
(and do some selenium hax for firefox so it works)
…ate. And update their values via JS.
(and do some selenium hax for firefox so it works)
…ate. And update their values via JS.
(and do some selenium hax for firefox so it works)
…ate. And update their values via JS.
See #2276 (comment) and related discussion.
Basically, if/when an image is sent to upload.py and returns a 415, the bug report form should do something intelligent. At the very least, remove the problematic image and inform the user we don't like it.
The text was updated successfully, but these errors were encountered: