Open Bug 730101 (prerendering) Opened 13 years ago Updated 2 years ago

Implement prerendering in Firefox

Categories

(Core :: DOM: Navigation, enhancement)

Product:
Core
Component:
DOM: Navigation
Type:
enhancement

Tracking

()

Status:
REOPENED

People

(Reporter: bug.zilla, Unassigned)

References

(Depends on 16 open bugs)

Details

(Keywords: dev-doc-needed, parity-chrome, parity-ie)

Can Firefox implement prerendering of pages like Chrome (http://code.google.com/chrome/whitepapers/prerender.html)? This is one of the main reasons users report that Chrome is "faster" than Firefox even though Javascript performance is probably not noticeably different.
I have tested this in Nightly 20.0a1 (2012-11-21) and prerender is not supported.
This is a great feature in Chrome that definitely does _not_ exist in Firefox. Firefox implements prefetching for single links into the cache. Prerender on Chrome will render an entire page in the background and hot-swap it when the URL is actually requested, so the page load is instantaneous. It strikes me that Firefox already has most of this functionality available in the bfcache (i.e. ability to have a hidden but active page that can be activated), so this should be relatively easy.
Whiteboard: [parity-chrome][parity-IE]
Severity: normal → enhancement
Component: General → Networking: Cache
Product: Firefox → Core
Version: 12 Branch → unspecified
OS: Windows 7 → All
Hardware: x86_64 → All
FWIW I will be mentoring an intern starting soon who will work on this.
Assignee: nobody → ehsan
I assume this will be based on data collected with the Network Seer?
(In reply to comment #8) > I assume this will be based on data collected with the Network Seer? It could be, yes. Once we have the support in the platform, we can look into various types of heuristics to determine when to prerender content, and the network seer could be one of them.
Assignee: ehsan → roshanvid
Component: General → Tracking
QA Contact: chofmann
Depends on: 1038993
Depends on: 1045212
Depends on: 1045215
Depends on: 1045759
Depends on: 1046291
Depends on: 1050456
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: dev-doc-needed
Depends on: 1052421
Depends on: 1052423
Depends on: 1057585
Depends on: 1058838
Depends on: 1058842
Depends on: 1058901
Depends on: 1058904
Depends on: 1058908
Depends on: 1058913
Depends on: 1058918
Depends on: 1058920
Depends on: 1058921
Depends on: 1058922
Depends on: 1058924
Depends on: 1058928
Depends on: 1058948
Depends on: 1058960
Depends on: 1058961
Depends on: 1058964
Depends on: 1058970
Depends on: 1058980
Depends on: 1060603
Depends on: 1061864
Depends on: 1069719
Depends on: 1069772
Depends on: 1085045
Assignee: roshanvid → ehsan
Depends on: 1117876
Alias: prerendering
Depends on: 1119866
Depends on: 1125351
Depends on: 1161646
Depends on: 1161663
Depends on: 1161665
Depends on: 1161679
Depends on: 1161680
Francisco, the FxOS 2.5 Architecture Evolution deliverables are dependent on this bug 730101 now that 1190805 is resolved as duplicate. is that correct? are we blocked in our delivery unless this is resolved in core?
Flags: needinfo?(francisco)
(In reply to Caitlin Galimidi [:c8o] from comment #13) > Francisco, > the FxOS 2.5 Architecture Evolution deliverables are dependent on this bug > 730101 now that 1190805 is resolved as duplicate. is that correct? are we > blocked in our delivery unless this is resolved in core? This is not happening by November, as there is no active developer working on it, and in top of that, the implementation will probably take much longer.
Flags: needinfo?(francisco)
Depends on: 1266910
Component: Tracking → Document Navigation
Depends on: 1302260
No longer depends on: 1276553
No longer depends on: 1276552
Mass bug change to replace various 'parity' whiteboard flags with the new canonical keywords. (See bug 1443764 comment 13.)
Keywords: parity-chrome, parity-ie
Whiteboard: [parity-chrome][parity-IE]
Assignee: ehsan → nobody
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID

Sorry, changing the resolution was an accident...

Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.