It's really easy to add an event listener in jQuery. It's equally easy to remove an event listener. You might want to remove a listener because you don't care to perform any actions on that event anymore, to reduce memory usage, or both. But let's say you've attached several listeners to the same event. How do you remove just one of them? Namespacing can help.
Welcome to THE ultimate resource for creatives. Up-to-the-minute updates from over 180 of your favorite design/dev/photo blogs around the web, all in one place... Stay a while!
We also contribute our own content to the design community. View our Original Posts.
I started a repository called WordCast under the Accessibility Project with the goal of converting that CodePen into a Node/Express/Socket.IO app that can brodcast subtitles. I’ve never built anything on any of these buzzwords I just typed, so I could definitely use some help.
Some heuristics on CSS that you can run on any site. Started with the sharing of that data from several popular sites. It's open source and I would think the most valuable feedback to give would be "what data would be useful to know about your CSS?"
The following is a guest post by Sebastian Ekström (@seb_ekstrom) a web developer from Sweden. I was interested in it because we talk a lot about CSS around here but have never talked about how CSS comes to be. CSS is just a syntax invented by people like you and me to try and solve problems. It's an extremely complicated thing involving: ease of use, backwards compatibility, browsers ability to implement with satisfactory speed, coverage of use cases, …
From the absolute basics in the first few minutes of ever using jQuery. Then onto the core fundamentals like selectors, basic methods, and events. Then into Ajax and data land. Then into templating, organization, and plugins. Then finishing with tools, performance, and workflow. …
Speaking of books, Dan Cederholm's new book on Sass is out. Forwarded by yours truly (!).
Scott Jehl (who is writing a book on the subject) on why you might want to progressively enhance on a component-by-component basis based on what that component needs, rather than a sweeping capability judgement based on the browser.
Make your own "tiny bootstraps, for every client."
If this is the first you've heard of it, it's a contest where you get a Photoshop document and have two weeks to convert it into HTML and CSS. You're judged on an established set of criteria.
It doesn't actually just plop the content from the referenced file where you call it though, like an @import does in CSS or and include does in a server side language. HTML could very much use that.
The following is a guest post by Rob Dodson (@rob_dodson). Rob and I were going back and forth in CodePen support getting Polymer (a web components polyfill, kinda) working on a demo of his. We did get it working, and things kind of evolved into this article. Take it away Rob.
Tabs are a simple design pattern in which a row of links are obviously clickable navigation and when a link is clicked, new content is shown. There are loads of variations of course, but it's one of the most ubiquitous navigation design patterns out there. When arranged in a horizontal row, it is also one of the least small-screen-friendly design patterns out there.
I agree with these general guidelines from Dudley Storey. Funny how these general-purpose length measurements have fallen into to some pretty specific niches.
The background property in CSS can accept comma separated values. "Multiple" backgrounds, if you will. You can also think of them as layered backgrounds since they have a stacking order. If we layer a transparent color over an image, we can "tint" that image. But it's not quite as obvious as you might suspect.
Recently at the CSS Dev Talk, I attended Clarissa Peterson's talk on responsive web typography. One part of it was about line length and readability. Of course, there are exceptions to every rule and your mileage may vary, but the traditional thinking is that body copy (long text, multiple paragraphs, takes more than a glance to read...) should be between 45 and 75 characters per line to be comfortable. Shorter is awkward, longer makes it easy to lose your place …