-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Internal URLs imported from Muon fail to resolve #2361
Comments
Following test plan from brave/brave-core#1021, my pinned tab with a PDF is imported (and opens fine) in b-c, but the normal tab which had a pdf is not imported into b-c. Is this expected? This is b-c after import from muon. I was expecting that the pinned 'PDFjs' tab wouldn't be there. |
@garrettr I believe the filtering logic might not be applying to pinned tabs |
@bsclifton Filtering logic should be applied in |
Verified passed with
Verification Passed on
Encounter an issue with pdf link: #2376 (comment)
|
Test Plan
brave/brave-core#1021
Description
Follow-up for #998 (comment).
The windows/tabs importer exactly re-creates the windows and tabs that were open in Muon in b-c. If any of the open tabs were showing a Muon internal URL (e.g.
about:preferences#payments
for Brave Payments,chrome-extension://...
for PDFs rendered by pdf.js), it probably won't resolve in b-c because most of the internal URLs have changed.A small subset of internal URLs, for example
about:history
, resolve correctly in both Muon and b-c.Steps to Reproduce
about:brave
.Actual result:
Expected result:
One of the two following scenarios should be implemented:
Reproduces how often:
Easily reproduced.
The text was updated successfully, but these errors were encountered: