Closed
Bug 941269
Opened 11 years ago
Closed 10 years ago
[User Story] Browser: Custom dialog
Categories
(Firefox OS Graveyard :: Gaia::System::Browser Chrome, defect)
Tracking
(feature-b2g:2.1, tracking-b2g:backlog)
RESOLVED
WORKSFORME
2.1 S2 (15aug)
People
(Reporter: pdol, Assigned: benfrancis)
References
Details
(Keywords: uiwanted, verifyme, Whiteboard: [ucid:System144, 1.4:P2, ft:systemsfe], system-browser, [p=2])
Attachments
(2 files)
User Story: e.g. As a user I want to be prompted to reload a POST HTTP request Acceptance Criteria: Functionality should match existing Browser functionality unless described otherwise in UX spec. Note: This bug is mainly to ensure this use case is already satisfied after the Browser becomes part of System.
Reporter | ||
Updated•11 years ago
|
Blocks: browser-chrome-mvp
Updated•11 years ago
|
Component: Gaia::System → Gaia::System::Browser
Updated•11 years ago
|
No longer blocks: browser-chrome-mvp
Reporter | ||
Updated•11 years ago
|
Blocks: browser-chrome-mvp
Assignee | ||
Comment 1•10 years ago
|
||
Does QA have an existing test case for this for the browser app so we can test to see if it's implemented in the system? You just need to submit a form via a POST request then reload the page to see a warning dialog, but I'm struggling to find an example!
Keywords: qawanted
Comment 2•10 years ago
|
||
(In reply to Ben Francis [:benfrancis] from comment #1) > Does QA have an existing test case for this for the browser app so we can > test to see if it's implemented in the system? > > You just need to submit a form via a POST request then reload the page to > see a warning dialog, but I'm struggling to find an example! Naoki would be a good person to ask about this. Switching this to needinfo.
Flags: needinfo?(nhirata.bugzilla)
Keywords: qawanted
Assignee | ||
Comment 3•10 years ago
|
||
Estimating as 2 points. This is relatively easy to implement if we don't have it already as we've done it in the browser app, it can just be a bit tricky to test.
Whiteboard: [ucid:System144, 1.4:P2, ft:systems-fe], system-browser → [ucid:System144, 1.4:P2, ft:systems-fe], system-browser, [p=2]
Not sure if this is what you're looking for, ben? Open the html and it will go to google as a post. If you refresh the browser it should give you the error message. To note, I didn't write the script... just found it on the web.
Flags: needinfo?(bfrancis)
Updated•10 years ago
|
Flags: needinfo?(nhirata.bugzilla)
Updated•10 years ago
|
Blocks: 1.4-systems-fe
Flags: in-moztrap?(nhirata.bugzilla)
Updated•10 years ago
|
No longer blocks: 1.4-systems-fe
Reporter | ||
Updated•10 years ago
|
blocking-b2g: --- → backlog
feature-b2g: --- → 2.1
Updated•10 years ago
|
Whiteboard: [ucid:System144, 1.4:P2, ft:systems-fe], system-browser, [p=2] → [ucid:System144, 1.4:P2, ft:systemsfe], system-browser, [p=2]
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → bfrancis
Flags: needinfo?(bfrancis)
Assignee | ||
Comment 5•10 years ago
|
||
Unfortunately that example didn't work for me, but I managed to reproduce using the steps in bug 796661. Attaching a screenshot, I'm pretty confident this is to the UX spec.
Assignee | ||
Comment 6•10 years ago
|
||
Resolving as WORKSFORME. Flagging for QA and UX verification.
Updated•10 years ago
|
Target Milestone: --- → 2.1 S2 (15aug)
https://moztrap.mozilla.org/manage/case/15078/
Flags: in-moztrap?(nhirata.bugzilla) → in-moztrap+
Updated•9 years ago
|
blocking-b2g: backlog → ---
tracking-b2g:
--- → backlog
You need to log in
before you can comment on or make changes to this bug.
Description
•