Open Bug 1460185 Opened 7 years ago Updated 3 years ago

support Windows 10 Timeline in April Update

Categories

(Core :: Widget: Win32, defect, P3)

Unspecified
Windows 10
defect

Tracking

()

People

(Reporter: lolipopplus, Unassigned)

References

()

Details

(Keywords: parity-chrome, parity-edge, Whiteboard: widget-next,[sci-exclude])

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:61.0) Gecko/20100101 Firefox/61.0 Build ID: 20180507191226 Steps to reproduce: Install system May accumulative update, update chrome canary to 68 branches Actual results: N/A Expected results: Firefox visit history should be available from Windows 10 Timeline as a Edge & Chrome parity feature.
Severity: normal → enhancement
Component: Untriaged → General
OS: Unspecified → Windows
Hardware: Unspecified → x86_64
This API has not allowed called unless UWP works yet.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
non-uwp apps can use it now: – Use the MS Graph REST API – Use the WinRT API after they call SetActivitySourceHost() explicitly on the UserActivityChannel
Status: RESOLVED → UNCONFIRMED
Component: General → Tabbed Browser
Hardware: x86_64 → Unspecified
Resolution: INVALID → ---
Version: 60 Branch → Trunk
Severity: enhancement → normal
Component: Tabbed Browser → Bookmarks & History
OS: Windows → Windows 10
Whatever we decide to do, we'll need platform support, so moving this to widget win32 for evaluation, we're open with hooking up history to whatever is decided.
Component: Bookmarks & History → Widget: Win32
Product: Firefox → Core
(In reply to lolipopplus from comment #2) > This API has not allowed called unless UWP works yet. How did Chrome insert the history into timeline at that time?
(In reply to Masatoshi Kimura [:emk] from comment #5) > How did Chrome insert the history into timeline at that time? From my knowledge: undocumented APIs. I didn't investigate very far.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P2
Priority: P2 → P3
Whiteboard: widget-next
Whiteboard: widget-next → widget-next,[sci-exclude]
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.