[Bug 60848] Sometimes closing an overlay triggers browser back behavior

2014-07-21 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=60848 --- Comment #11 from Ryan Kaldari rkald...@wikimedia.org --- *** Bug 65041 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.

[Bug 60848] Sometimes closing an overlay triggers browser back behavior

2014-07-21 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=60848 Ryan Kaldari rkald...@wikimedia.org changed: What|Removed |Added See Also|

[Bug 60848] Sometimes closing an overlay triggers browser back behavior

2014-04-30 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=60848 Jon jrob...@wikimedia.org changed: What|Removed |Added CC||ryasm...@wikimedia.org ---

[Bug 60848] Sometimes closing an overlay triggers browser back behavior

2014-03-04 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=60848 Jon jrob...@wikimedia.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 60848] Sometimes closing an overlay triggers browser back behavior

2014-02-26 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=60848 --- Comment #8 from Jon jrob...@wikimedia.org --- *** Bug 61966 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.

[Bug 60848] Sometimes closing an overlay triggers browser back behavior

2014-02-05 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=60848 --- Comment #4 from Ryan Kaldari rkald...@wikimedia.org --- If we're going to treat overlays as pages rather than overlays, the interface should reflect that. In other words, we should be using back arrows instead of close 'x's. Otherwise the

[Bug 60848] Sometimes closing an overlay triggers browser back behavior

2014-02-05 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=60848 Jon jrob...@wikimedia.org changed: What|Removed |Added Severity|normal |enhancement -- You are

[Bug 60848] Sometimes closing an overlay triggers browser back behavior

2014-02-05 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=60848 Brandon Harris bhar...@wikimedia.org changed: What|Removed |Added CC|

[Bug 60848] Sometimes closing an overlay triggers browser back behavior

2014-02-05 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=60848 Kaity Hammerstein khammerst...@wikimedia.org changed: What|Removed |Added CC|

[Bug 60848] Sometimes closing an overlay triggers browser back behavior

2014-02-05 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=60848 --- Comment #7 from kenan wang kw...@wikimedia.org --- Yes I would expect it to close the notifications so you can see the article. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.

[Bug 60848] Sometimes closing an overlay triggers browser back behavior

2014-02-04 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=60848 --- Comment #1 from Bingle bingle-ad...@wikimedia.org --- Prioritization and scheduling of this bug is tracked on Mingle card https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1666 -- You are receiving this mail because: You are

[Bug 60848] Sometimes closing an overlay triggers browser back behavior

2014-02-04 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=60848 --- Comment #2 from Juliusz Gonera jgon...@wikimedia.org --- If you type that link directly in the browser then unfortunately that's what will happen. It basically goes to the previous item in browser's history. -- You are receiving this mail

[Bug 60848] Sometimes closing an overlay triggers browser back behavior

2014-02-04 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=60848 --- Comment #3 from Jon jrob...@wikimedia.org --- To be fair that's how the web works... not sure we should complicate things by trying to change that. I'd suggest this is a WONTFIX... If you followed a link to the editor from twitter would