You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that the config behind the build command is transpiling incorrectly for mobile browsers.
Expected Behavior
Array.map() methods, when used to populate dropdowns, should behave exactly the same on desktop, and on mobile browsers.
Observed Behavior
When deploying builds using npm run build, dropdowns populate as expected for deployed React web apps on both desktop and mobile browsers, but attributes (e.g. onClick) do not seem to be populating correctly behind the scenes. For example, a dropdown item that navigates the user to another page of a React project will correctly route them when they use a desktop browser (including in mobile view with Chrome dev tools), but the same dropdown will not consistently route them correctly when they access the same React app with a mobile browser on a mobile device.[1]
It seems that the config behind the
build
command is transpiling incorrectly for mobile browsers.Expected Behavior
Array.map() methods, when used to populate dropdowns, should behave exactly the same on desktop, and on mobile browsers.
Observed Behavior
When deploying builds using
npm run build
, dropdowns populate as expected for deployed React web apps on both desktop and mobile browsers, but attributes (e.g.onClick
) do not seem to be populating correctly behind the scenes. For example, a dropdown item that navigates the user to another page of a React project will correctly route them when they use a desktop browser (including in mobile view with Chrome dev tools), but the same dropdown will not consistently route them correctly when they access the same React app with a mobile browser on a mobile device.[1]See a full description of this issue, with screenshots and code samples, here: https://stackoverflow.com/questions/60494492/react-web-app-routing-works-on-desktop-incl-mobile-dev-view-but-not-on-mobil
The text was updated successfully, but these errors were encountered: