Open kbecciv opened 1 year ago
Also, I assume you tested other browsers and the behavior is different there? If so, which ones did you test?
@iwiznia
did you find a chrome bug report for this?
No
How do you know it is a bug that will be fixed vs expected behavior that will never change?
We don't know that
What are the alternatives?
Prevent image from loading when offline, but this would also mean to not load images that are cached. The drawback is cached images will not work once we go offline.
I assume you tested other browsers and the behavior is different there? If so, which ones did you test?
Tested on Firefox and WebKit
Prevent image from loading when offline, but this would also mean to not load images that are cached. The drawback is cached images will not work once we go offline.
Yeah, that's not great. Any others?
Also, we sure that's chrome's behavior and that's not some quirk of our code? Can you create a small test file showing the broken behavior of chrome please?
I did a small test with this file and can't reproduce the behavior you mention:
<html>
<body>
<img id='a' src="https://www.algosolutions.com/wp-content/uploads/2021/05/algo.png">
<button onClick="document.getElementById('a').remove(); document.body.innerHTML = '<img id=\'a\' src=\'https://www.algosolutions.com/wp-content/uploads/2021/05/algo.png\'>'">load</button>
Steps:
The bug only exists for css urls, use background-image
style instead of img
tag. I guess the alternative here is to use some RN image library that does not relay on background-image style or make RNW does not relay on it.
Ohh I see, can you provide a simple file like I did that shows this behavior please? I am not sure I get exactly what you mean
RNW seems to use the img tag just for accessibility(?) The img
seems to have opacity set to 0
.
I will work on a reproduction example that is outside E/App.
@iwiznia, @s77rt, @sophiepintoraetz, @crazy-coding Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
@iwiznia Any thoughts here? Should we look for why RNW uses background-image in the first place? It's pretty weird
Oh sorry, we had a discussion in slack (prviate channel though https://expensify.slack.com/archives/C03TQ48KC/p1689198663603339) and forgot to update here.
I think we are not going to add hacks to work around a browser bug and we probably should instead report this as a bug to chrome and see if they accept it or not.
Awesome thanks!
I doubt this will have much activity for a while since we need to wait what chrome says, so not unassigning myself, but if this needs an engineer in the future, @sophiepintoraetz please unassign and re-assign another engineer since I am going on sabbatical
I'll drop this one to weekly in the meantime - @s77rt let me know how this bug report tracks!
I think the issue has been accepted. Still untriaged though
Still waiting on Chrome!
This issue has not been updated in over 15 days. @iwiznia, @s77rt, @sophiepintoraetz, @crazy-coding eroding to Monthly issue.
P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!
Still waiting on Chrome. Keeping this as Monthly seems good.
Hey @s77rt, can you please take a loot at https://github.com/Expensify/App/issues/25447 and confirm if it's a dupe?
@thesahindia Seems like a dupe.
@dukenv0307 The reported bug on Chrome has been accepted and it's in open state for now. The best solution is to do nothing. This is not.a bug from our end.
Thanks for the confirmation @s77rt.
Thinking on this, do we close the issue? Seeing as it's still with Chrome (are they guaranteed to fix it?), and we can't do anything about it? @s77rt @iwiznia
We can do that or keep it open, does not bother much 🤷
I think they have a commit to fix the bug https://chromium.googlesource.com/chromium/src/+/c04f52aa42ef09dd9cc5e50b8b3b1809165a6a3b Not sure if this released to the latest version or not yet (seeing the issue still marked as Open I guess not)
@iwiznia, @s77rt, @sophiepintoraetz, @crazy-coding, this Monthly task hasn't been acted upon in 6 weeks; closing.
If you disagree, feel encouraged to reopen it -- but pick your least important issue to close instead.
Issue is reproducible in build v1.4.69-0 Offline avatar gets grey and is not updated until page refresh.
https://github.com/Expensify/App/assets/115492554/4ad09cdb-55af-4368-ba68-73c8445cf073
@izarutskaya Is this still reproducible? Can you try update the browser first
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Expected Result:
Avatar should be updated to default online image
Actual Result:
Offline avatar gets grey and is not updated until page refresh.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.6.0
Reproducible in staging?: Yes
Reproducible in production?: yes
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/93399543/234732792-7e5240dd-2119-40a7-aae9-42fae89cfc9d.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub
Upwork Automation - Do Not Edit