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
{{ message }}
Instantly share code, notes, and snippets.
Irae Carvalho
irae
Programming and creating websites since 1999 and Full Time Front End Engineer since 2005, Full Stack since 2015. User-focused design enthusiast.
I love how mapDispatchToProps avoids a bound method on render
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Is including react-dom/server in your bundle a bad idea?
Here at work, a colleague asked if we were doing a mistake by using the ReactDOM.renderToStaticMarkup on the client side. The idea was to use that for a rich text editor that needs some raw HTML inside.
Here is how the code looks like:
importReactfrom'react';importReactDOMfrom'react-dom';importReactDOMServerfrom'react-dom/server';// the whole classvarmarkupToInsert=ReactDOMServer.renderToStaticMarkup(someReactElements);
require('react') and Browsefiry versus CDN React sizes
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
UI is blocked while any animation/transitions, taps and swipes are ignored
UI is blocked while any animation/transitions, taps and swipes are ignored
This is present overall in many interactions on the whole OS. While some animation is happening, even if I can already see the end result or if I know where I am navigating to, and I start swiping on tapping on the screen, the OS won't recognize until animation ends. At many times this "trows away" my input.
Although the video is comparing iOS 8 to iOS 3, this is still true and reproducible on iOS 9 beta. The video also talks about multi-tasking and switching apps, but this issue is not asking to address this particular interaction, as it's out of scope (although is fair to assume that improvements can be made as a separate issue).
I can observe two groups of OSs that I can reproduce:
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters