-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Bump react-native-web to 0.15.7 react to 17.0.2 #3215
Conversation
👍 |
There is a bug on |
FYI, conflicts |
Updated |
Damn, sorry @marcaaron -- some recent merge has triggered further conflicts |
Thanks, conflicts fixed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes look good and it tested well. Added a few questions
Gonna run through platform tests again since we just updated 7 zillion other things. |
Ok ready for review again |
/** | ||
* Determines whether the drawer is currently open. | ||
* | ||
* @returns {Boolean} | ||
*/ | ||
function isDrawerOpen() { | ||
return getIsDrawerOpenFromState(navigationRef.current.getRootState().routes[0].state); | ||
} | ||
|
||
export default { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Was this just removed for cleanup?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good. Ran through all flow I could think of without running into any issues.
🚀 Deployed to staging in version: 1.0.65-10🚀
|
Links are opening in the same tabExpected ResultLinks should open in a different tab Actual resultLinks are opening in the same tab Action Performed
PlatformWeb ✔️ Notes/images/video |
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
|
Hmm.. I think this is possibly related to this PR -> #3066 And not this one... cc @roryabraham - also lmk if that's incorrect and I can look into this some more. |
I don't think so ... I believe I checked regular links in the testing + QA steps of that PR. Also the |
Ok cool maybe it is related to |
If it helps, I'm pretty sure I didn't try opening links during testing. |
Copied the markup from one of these links and got this <a href="https://google.com" role="link" class="css-reset-4rbku5 css-cursor-18t94o4 css-text-901oao css-textHasAncestor-16my406" style="color: rgb(1, 133, 255); font-family: GTAmericaExp-Regular; font-size: 15px; line-height: 20px; text-decoration-color: rgb(1, 133, 255); text-decoration-line: underline;">https://google.com</a> so seems like the target is not getting passed now, but unsure why. |
Seems like we need to use Fix PR incoming. |
It looks like this PR is responsible for #3512 It seems like the new react native web is eating shortcuts for some reason when focused on inputs. This happens when doing cmd+k for the sidebar, and pressing escape to remove the sidebar. |
I had a quick look through the It's also odd that no one else has reported this issue (the release was back in April). |
It looks to me like this |
I'm leaning towards reverting this PR as it introduced two regressions that block our N5 build and we're struggling to make progress on these fixes. Does anyone disagree? It's a bit of a pain to revert, CP and review again but I can't see much progress being made here soon and we're hoping to release on Monday. |
If we're planning on releasing Monday I agree, we should just revert. These are changes to 2 of our core components and if we already have 2+ regressions, I would be willing to bet there are more |
If we want to revert this then we will need to also roll back #3486 Also heads up, if we wants this to happen before Monday please get someone else to help with the revert and testing as I can't manage this. We might also want to keep an eye on the
|
I also can't take care of this 😅 I'm working half days Monday/Tuesday |
I was mistaken. This PR didn't introduce the issue -- it started occurring after |
🚀 Deployed to production in version: 1.0.68-4🚀
|
Details
cc @roryabraham @sketchydroide
Coming from #2939
I'm gonna recommend that we do not update to react-native-web 0.16 yet because there is a change to
EventEmitter
that is causing logs to stream in the console. Probably this will change when we update other dependencies that reference the more recent versions ofreact-native
.Fixed Issues (Snyk PR)
#2939
Tests
QA Steps
Test opening links and verify they open in new tabs on web
Test for general regressions in all platforms
Tested On
Screenshots
Web
Mobile Web
Desktop
iOS
Android