Besides the much talked about video tag, HTML5 also introduced a couple of new input types, one of which is a rather interesting range input type which basically translates to a slider bar control:
The range input type is currently supported by the latest versions of Safari, Chrome and Opera while other browsers such as Firefox simply treat the field as a textbox.
There are four available attributes – min, max, step and value. min and max should be self explanatory, step determines the size of each increment/decrement and value is the current value of the slider and also determines the placement of the slider when the element is loaded (if not specified, the slider will appear at the centre of the control when it’s first loaded):
<input type="range" min="0" max="200" step="5"></input>
<input type="range" min="0" max="200" value="0" step="5"></input>
I talked about the new border radius property being introduced in CSS3 in my previous blog post, and with a little JQuery I’ve put together a quick demo here of how a 400px by 400px square looks as the border radius changes.
I specialise in rapidly transitioning teams to serverless and building production-ready services on AWS.
Are you struggling with serverless or need guidance on best practices? Do you want someone to review your architecture and help you avoid costly mistakes down the line? Whatever the case, I’m here to help.
Check out my new course, Complete Guide to AWS Step Functions. In this course, we’ll cover everything you need to know to use AWS Step Functions service effectively. Including basic concepts, HTTP and event triggers, activities, callbacks, nested workflows, design patterns and best practices.
Here is a complete list of all my posts on serverless and AWS Lambda. In the meantime, here are a few of my most popular blog posts.
- Lambda optimization tip – enable HTTP keep-alive
- You are thinking about serverless costs all wrong
- Many faced threats to Serverless security
- We can do better than percentile latencies
- I’m afraid you’re thinking about AWS Lambda cold starts all wrong
- Yubl’s road to Serverless
- AWS Lambda – should you have few monolithic functions or many single-purposed functions?
- AWS Lambda – compare coldstart time with different languages, memory and code sizes
- Guys, we’re doing pagination wrong