Closed Bug 648628 Opened 13 years ago Closed 13 years ago

disable share button for a directed share type without a direction

Categories

(Cloud Services :: Share: Web Client, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: clarkbw, Unassigned)

References

Details

Attachments

(1 file)

in other words if you select twitter direct message but don't specific a recipient we should disable the share button.

Since I despise disabled buttons, it would be better to have a button that looks disabled and opens an alert when clicked with a message like: "Please enter a recipient for your share".
Wait... a UX person who prefers modal alerts over button disabling?  Crazy talk.
I might be cheating a bit here.  Since we don't yet have a "notification space" where I can easily put messages the JS alert should work since I'm assuming that with the new alerts (which are flat and embedded in the tab) it will remain within the panel.
(In reply to comment #2)
> I might be cheating a bit here.  Since we don't yet have a "notification space"
> where I can easily put messages the JS alert should work since I'm assuming
> that with the new alerts (which are flat and embedded in the tab) it will
> remain within the panel.

Unfortunately you're assuming wrong. window.alert() from the panel browser will present an old modal alert in chrome.

I think we should do the error notification in content rather than surfacing a dialog.
Attachment #525521 - Flags: review?(mixedpuppy)
The pull request review for this is actually just a pointer to the commit log for the hotfix branch: I should have done a separate branch of the hotfix branch to do this fix, but I goofed up.

With the changes, if no direct message recipient, the to field is highlighted with a red border and an an inline message is placed next to the disabled share button.

There is also checking for invalid recipients now, and if there is one, a similar treatment: red border highlight and inline message next to disabled share button.
Comment on attachment 525521 [details]
Pointer to pull request

nice!

Actual diff is at 

https://github.com/mozilla/f1/compare/master...hotfix%2F648372

That is a diff for the entire hotfix we'll be doing against the f1.momo live server.
Attachment #525521 - Flags: review?(mixedpuppy) → review+
Blocks: 647578
The changes have been merged into web/dev/1 which is used by the integrated Fx UI. With that merge, the fix is complete:
https://github.com/mozilla/f1/commit/bc0f61c89619c9504a0556c4780c897429888c48
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: