Closed
Bug 595432
Opened 14 years ago
Closed 14 years ago
Invalid form popup should use an arrow panel
Categories
(Firefox :: General, defect)
Firefox
General
Tracking
()
RESOLVED
FIXED
Firefox 4.0b8
People
(Reporter: mounir, Assigned: mounir)
References
Details
Attachments
(3 files, 1 obsolete file)
4.04 KB,
patch
|
Gavin
:
review+
limi
:
ui-review+
|
Details | Diff | Splinter Review |
42.69 KB,
image/png
|
Details | |
28.26 KB,
image/png
|
Details |
Unfortunately the invalid form popup is going to land without an arrow panel. We should change that as soon as bug 554937 is pushed.
Assignee | ||
Comment 1•14 years ago
|
||
Assignee | ||
Comment 2•14 years ago
|
||
Comment 3•14 years ago
|
||
Looks good! Although I'd suggest much less glass border (or any border for that matter) since this isn't a full-sized arrow panel.
Assignee | ||
Comment 4•14 years ago
|
||
Limi, this is changing the style of the popup when the users try to submit an invalid form. I think that's better because it's now consistent with most other popups and the user will understand that's a message from the UA and not the website. In addition, it's nicer. But that's far from the initial draft you did for this popup so let me know if you are fine with the change.
Sent to the try server if you need to test something:
http://ftp.mozilla.org/pub/mozilla.org/firefox/tryserver-builds/mlamouri@mozilla.com-50c95438d689
(screenshots will come)
Assignee: nobody → mounir.lamouri
Attachment #484644 -
Attachment is obsolete: true
Status: NEW → ASSIGNED
Attachment #485733 -
Flags: ui-review?(limi)
Attachment #485733 -
Flags: review?(gavin.sharp)
Assignee | ||
Comment 5•14 years ago
|
||
On Windows too, the style will now be the default arrow panel default style (not the same whether Aero is enabled or not). I will try to attach screenshots when builds will be done.
On Linux, the style is the same given that arrow panels are not enabled.
The idea is to judge the general aspects. For small tweaks like those mentioned in comment 3, bug 602500 would be appropriate.
Comment 6•14 years ago
|
||
(In reply to comment #5)
> On Linux, the style is the same given that arrow panels are not enabled.
Stephen Horlander is working on a patch for the linux arrow panel styling right now, so there should probably be a follow-up bug to get rid of that #invalid-form-popup styles in browser.css if it's left in for now. (See bug 577930 and bug 604257.)
Assignee | ||
Comment 7•14 years ago
|
||
The arrow isn't exactly on the input field but this is the case for all arrow panels on Windows (only tested with Aero disabled). I should check if we have a bug filed for that.
Assignee | ||
Comment 8•14 years ago
|
||
Comment on attachment 486022 [details]
Style change for Windows
I thought the style would have been a bit nicer with Aero but it looks like it isn't... :(
Attachment #486022 -
Attachment description: Style change for Windows (non Aero) → Style change for Windows
Comment 9•14 years ago
|
||
Assignee | ||
Comment 10•14 years ago
|
||
(In reply to comment #9)
> (In reply to comment #7)
> > I should check if we have a bug filed for that.
>
> Bug 606343?
Seems like it. Thanks :)
Assignee | ||
Updated•14 years ago
|
Whiteboard: [needs review]
Comment 11•14 years ago
|
||
Comment on attachment 485733 [details] [diff] [review]
Patch v1
As far as what it's attempting to do, this patch/styling seems fine to me.
I'm not entirely sold on the reason why we should use doorhanger-style notifications here as opposed to something that is closer to tooltips (do we really want to emphasize that it's the browser and not the web site telling you to do this when the website has control of the actual text?), but I'm fine with shipping this in the next beta(s) to get feedback.
Attachment #485733 -
Flags: ui-review?(limi) → ui-review+
Assignee | ||
Comment 12•14 years ago
|
||
(In reply to comment #11)
> Comment on attachment 485733 [details] [diff] [review]
> Patch v1
>
> As far as what it's attempting to do, this patch/styling seems fine to me.
>
> I'm not entirely sold on the reason why we should use doorhanger-style
> notifications here as opposed to something that is closer to tooltips (do we
> really want to emphasize that it's the browser and not the web site telling you
> to do this when the website has control of the actual text?), but I'm fine with
> shipping this in the next beta(s) to get feedback.
I think the doorhanger style is nicer than the tooltip style but the main reason is that authors can't style the panel so having a browser-style panel might be better because users may understand that this is a message from the browser and not the website. That way, authors might use it more because, right now I have the feeling that they are reluctant because they can't style it.
Assignee | ||
Comment 13•14 years ago
|
||
Do you think you can get this reviewed before b8 freeze? It would be nice to get feedbacks from web authors as soon as possible.
Comment 14•14 years ago
|
||
Comment on attachment 485733 [details] [diff] [review]
Patch v1
Why are you leaving the style rule in browser.css for gnomestripe?
Why did you add the orient=vertical to the panel?
Does the max-width rule for the description actually work?
Assignee | ||
Comment 15•14 years ago
|
||
(In reply to comment #14)
> Comment on attachment 485733 [details] [diff] [review]
> Patch v1
>
> Why are you leaving the style rule in browser.css for gnomestripe?
Because there is no arraw type panel for gnomestipe yet :(
> Why did you add the orient=vertical to the panel?
>
> Does the max-width rule for the description actually work?
Yes, with orient=vertical. Without orient=vertical, it doesn't work.
Assignee | ||
Updated•14 years ago
|
Attachment #485733 -
Flags: approval2.0?
Comment 16•14 years ago
|
||
What is the effect of this on extension compatibility?
Assignee | ||
Comment 17•14 years ago
|
||
(In reply to comment #16)
> What is the effect of this on extension compatibility?
The orient change shouldn't have any effect given that AFAIK, panels have orient=vertical but not arrowpanels. So I've added that to keep the same behavior.
The only possible issue is if an extension is changing the style of the panel based on the current style (like adding red borders). With this change, the result might be ugly.
But I don't think that should happen given that this has been added in b7 (so, quite recently) and it's obvious that the current style should be changed (and I said so in my blog post for this feature) and why an extension would do that?
Comment 18•14 years ago
|
||
Blocking to get this feature finalized for Firefox 4.
blocking2.0: --- → betaN+
Updated•14 years ago
|
Attachment #485733 -
Flags: review?(gavin.sharp) → review+
Assignee | ||
Updated•14 years ago
|
Whiteboard: [needs review] → [needs review][needs approval]
Assignee | ||
Updated•14 years ago
|
Whiteboard: [needs review][needs approval] → [needs approval]
Assignee | ||
Updated•14 years ago
|
Attachment #485733 -
Flags: approval2.0?
Assignee | ||
Updated•14 years ago
|
Whiteboard: [needs approval]
Assignee | ||
Comment 19•14 years ago
|
||
Pushed:
http://hg.mozilla.org/mozilla-central/rev/2f448cda82bd
bug 615979 will be used to update the gnomestrip (GTK) theme as soon as arrow panel will be enabled for GTK.
Target Milestone: --- → Firefox 4.0b8
Assignee | ||
Updated•14 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•