In order for web pages and applications to be truly accessible, a user must be able to do anything with a keyboard that can be done with a mouse. When it comes to drag and drop, I’m often asked if it is acceptable to provide an accessible workaround.
Let’s start by understanding what actually happens to our CSS code when we load up a web page in a browser. When a browser starts to load the initial HTML file, it takes the loaded HTML code and parses it, which means that it will decode the code line by line.
Um. You should change your title to “Understanding static in React and possibly future versions of JS”. Static properties (not methods) are available in React, because of this Babel plug-in, which is a precursor to this ES suggestion (which is not yet implemented).
React Hooks are a shiny new proposal that will allow you to write 90% cleaner React. According to Dan Abramov, Hooks are the future of React. That sounds good and all but what are Hooks and how will they help me write better code? Glad you asked.
There seems to be a lot of misconceptions about the different methods of setting up event handlers in React, especially about what goes on behind the scenes. Here I tried to group together some of the fundamental aspects that get frequently left out. First of all look at these two blocks of code.
Inspired by a technical talk I’m giving for a Meetup, I wanted to take a moment and share what I’ve learned on React component patterns. Components are the heart of React, so understanding how to utilize them is paramount to creating great design structures.
If you have been doing some React development recently, you must have come across terms like HOCs and Render Props. In this article, we’ll go deep into both these pattern to understand why we need them and how we can correctly use them to build better react applications.