Closed
Bug 1075978
Opened 10 years ago
Closed 10 years ago
Loading a second call URL does not update the call URL
Categories
(Hello (Loop) :: Client, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: u279076, Unassigned)
Details
Attachments
(1 file)
248.50 KB,
image/png
|
Details |
Tested on today's Nightly on Mac OS X: 1. User X generates a call URL, copies it and shares it with User Y 2. User Y loads the URL > Standalone page loads and displays the call URL 3. User X generates a new call URL, copies it and shares it with User Y 4. User Y loads that new URL > Standalone page still displays the original call URL, not the new one A screenshot is attached which shows the loaded URL (location bar) being different than what the Standalone page is showing.
FWIW, also reproduces in Aurora.
status-firefox34:
--- → affected
status-firefox35:
--- → affected
Comment 2•10 years ago
|
||
I had a similar problem today with Nightly. This is related to the way the browser works with hash. Since the URL before the hash doesn't change, the page doesn't reload. I think loop-client should handle the onHashChange event to handle that.
Comment 3•10 years ago
|
||
As written, this is actually not a bug in Loop or Firefox (the main browser). We would need to change the format of the URL to not use "#" for the parameter.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
status-firefox34:
affected → ---
status-firefox35:
affected → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•