[PM-15065] Vault Loading on empty tabs #12059
Open
+37
−8
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🎟️ Tracking
PM-15065
Slack Discussion
📔 Objective
When on a non-standard page or empty tab is focused when opening the extension, the vault was taking longer than expected to load. This was caused from a message never being received in the
collectPageDetailsFromTab$
observable.sendMessage
fails in Chrome and Firefox. That error was ignored in thetabSendMessage
, I now rejected the promise to surface the error.url
, I added a check for that as there wouldn't be autofill information (to my knowledge)Rejecting the promise
This approach falls in line with what is happening but it is also introducing a new set of logic where
tabSendMessage
is called. Scanning the codebase there are places that have error handling and some that do not. If there is a more idiomatic approach, let me know!📸 Screenshots
chrome-after.mov
firefox-after.mov
safari-after.mov
🦮 Reviewer guidelines
:+1:
) or similar for great changes:memo:
) or ℹ️ (:information_source:
) for notes or general info:question:
) for questions:thinking:
) or 💭 (:thought_balloon:
) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion:art:
) for suggestions / improvements:x:
) or:warning:
) for more significant problems or concerns needing attention:seedling:
) or ♻️ (:recycle:
) for future improvements or indications of technical debt:pick:
) for minor or nitpick changes