Closed Bug 773898 Opened 13 years ago Closed 9 years ago

Implement relative link support for app:// scheme

Categories

(Core :: Networking, defect)

Product:
Core
Component:
Networking
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WONTFIX
Project Flags:
blocking-kilimanjaro +
blocking-basecamp -

People

(Reporter: briansmith, Unassigned)

References

Details

+++ This bug was initially created as a clone of Bug #769350 +++ We need to support relative links so that app developers can write <img src="myimage.jpg"/>, but the app:// scheme currently has the URI_NORELATIVE flag. It seems that URI_NORELATIVE is not actually enforced anywhere (see bug 652114) so this bug may simply be about removing the URI_NORELATIVE flag and adding a test that relative URLs work. (Common sense says that relative links in the app:// scheme must already be working, otherwise people would already be having a bad time.)
blocking-basecamp: --- → ?
Blocking+. This seems like a developer ergonomics issue that would cause much suffering if it didn't work.
blocking-basecamp: ? → +
blocking-kilimanjaro: --- → +
Comment #1 is right : we should remove the URI_NORELATIVE flag, it is ignored anyway. Gaia makes extensive use of relative links.
Given that this flag doesn't actually do anything, and gaia is working fine, let's not block on this.
blocking-basecamp: + → -
Unrelated to updates.
No longer blocks: b2g-updates
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.