-
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
[Desktop] race condition with Greaselion and localizations #12264
Comments
We think this is caused by or related to this upstream bug: https://bugs.chromium.org/p/chromium/issues/detail?id=83549. |
|
Reproduced on
Steps:
Note: Browser restart fixes the issue |
Removed |
When this fails for me, it's due to the contents of the following directory being deleted: It seems like there are two problems here:
|
I often see Failed to fetch user details for : Missing auth headers as well. You can trigger this message by switching away from Twitter, and back. It's fairly easy to reproduce in my experience. This makes sense, since I am apparently also never able to actually trigger the const handleOnSendHeadersWebRequest = (mediaType: string, details: any) => {
if (mediaType !== types.mediaType || !details || !details.requestHeaders) {
return
}
if (auth.processRequestHeaders(details.requestHeaders)) {
tipping.configure()
}
} That handler is registered successfully, but never called: webRequestHandlers.registerOnSendHeadersWebRequest(
types.mediaType,
types.sendHeadersUrls,
types.sendHeadersExtra,
handleOnSendHeadersWebRequest)
tabHandlers.registerOnUpdatedTab(types.mediaType, handleOnUpdatedTab) |
@jonathansampson I've got a fix for the localizations bug teed up, I just need to clean it up and PR it (most likely in the morning at this point). I have seen that Twitter error message, but I think it's probably unrelated to this. As long as tipping and the panel works correctly, it should be doing the right thing. It will often write out that message due to the timing of when we receive the auth cookie, but it's typically a benign message. It's weird if you're not seeing it triggered, though. Most of the publisher sites are split into two separate scripts (and soon three), so it could possibly be that only one is receiving that? |
@emerick Tipping isn't working when I see this error; clicking the inline tipping button raises the following: Failed to fetch tweet metadata for [object HTMLElement]: Error: Missing auth headers
at api.ts:19
at new Promise (<anonymous>)
at sendAPIRequest (api.ts:11)
at Module.getTweetDetails (api.ts:82)
at getMediaMetaData (tipping.ts:22)
at HTMLButtonElement.tipButton.onclick (tipping.ts:140) |
@jonathansampson OK, gotcha - then it's definitely not what I was thinking. Do you mind creating a new issue with that info and the steps to repro that you mentioned earlier and we'll prioritize it? Thank you! |
Verified passed with
Verified test plan from brave/brave-core#7141 (comment) Opened multiple tabs w/ in-line tip buttons. Examples:
Generally confirmed:
Verification passed on
Verified test plan from brave/brave-core#7141 (comment) Opened multiple tabs w/ in-line tip buttons. Examples:
|
Description
I noticed that the "Tip" text wasn't displaying next to the in-line BAT logo on twitter. When this happens, if you click on the in-line tip icon, sometimes (not always) nothing will happen (no tip banner opens).
Per discussion with @emerick there is a race condition with localizations that causes the text to not display properly. A browser restart fixes this.
Steps to Reproduce
Unsure if the below will work 100% of the time:
Actual result:
No "Tip" text next to the BAT logo and when you click on it, the banner may or may not open.
Expected result:
should say "Tip" and "Tip" should change to orange when hovered over. Should be able to click on the BAT logo/text and the tip banner should be displayed.
Reproduces how often:
intermittent, race condition
Brave version (brave://version info)
Version/Channel Information:
Other Additional Information:
Miscellaneous Information:
cc @emerick @NejcZdovc
The text was updated successfully, but these errors were encountered: