Glenn Fleishman:

At an increasing number of publications, [curly quotes have] been ironed straight. This may stem from a lack of awareness on the part of website designers or from the difficulty in a content-management system (CMS) getting the curl direction correct every time. It may also be that curly quotes’ time has come and gone.

I know it’s highly uncool in this community to get quotes wrong and highly cool to remind people how to type them. I’m on the uncool side of the fence on this one. I go so far as to standardize on straight quotes on this site. I’m not worried about the encoding, but laziness is some part of it. It’s a weird key command (⌥ [) especially for coders who are so used to straight quotes being required. Not to mention a different key command for the closing version (e.g. ⌥ ⇧ ]), and both are even harder on any non-macOS system). Straight quotes of both varieties have a dedicated key.

You know what is a cool-these-days sentiment? The fact that language evolves, including written language. I’m not anti-curly-quotes, I just don’t care. If you’d like to write in straight quotes, but publish in curly quotes because “algorithmically, it’s a solved problem”, be my guest. Perhaps written English, on the web, has evolved to “whatever, either way”. Oooooo look at that period outside the straight quotes. I’m a loner, Dottie. A rebel.

Direct Link to ArticlePermalink

Has the Internet Killed Curly Quotes? is a post from CSS-Tricks

Source: Has the Internet Killed Curly Quotes?


The Year in Housing: The Middle Class Can’t Afford to Live in Cities Anymore

Cities are increasingly populated by lower-income people in subsidized housing and high income people prepared to pay $3,500 a month for a one-bedroom. The post The Year in Housing: The Middle Class Can’t Afford to Live in Cities Anymore appeared first on WIRED.
Source: The Year in Housing: The Middle Class Can’t Afford to Live in Cities Anymore

Open Source
Open gaming roundup for December 18 - 31, 2016

In this bi-weekly open gaming roundup, we take a look at the upcoming Nintendo console, System76’s joint effort with NVIDIA to fix driver bugs, and more.

Open gaming roundup for December 18-31, 2016

read more
Source: Nintendo Switch to use Vulkan, System76 aids in NVIDIA bug fixing, and more gaming news

Electronics For You

Here is a simple AF amplifier project based onefy tested77 TBA820M IC. This amplifier can deliver two-watt output power with 8-ohm speaker using a 12V power supply.

A 3-16V battery or an AC/DC adaptor can be used to power this circuit. Author’s prototype is shown in Fig. 1.

Circuit and working

Author’s prototype AF Amplifier
Fig. 1: Author’s prototype
Circuit diagram of the two-watt TBA820M AF amplifier
Fig. 2: Circuit diagram of the two-watt TBA820M AF amplifier

Circuit diagram of the two-watt TBA820M AF amplifier is shown in Fig. 2. An 8-ohm, 2W loudspeaker is connected to output pin 5 of IC1 through C5.

Pin 8 (ripple rejection) is connected to +Vcc through C6. Also, C7 is connected to positive and ground for noise filtering.

The post Two-Watt TBA820M AF Amplifier appeared first on Electronics For You.

Source: Two-Watt TBA820M AF Amplifier

Designing for “Show scroll bars”

In macOS, users have the ability to set when they want to see scrollbars in windows. This affects all windows in the operating system, including in web browsers. They have three choices:

  • Automatically based on mouse or trackpad
  • When scrolling
  • Always

Which means you are either in a state where you see them all the time, or a state where you only see them once scrolling has been started through some other means.

The Always option is pretty straightforward. If the window needs scrolling, the scroll bar will be there. If not, it won’t be. If the scrollbar is there, it squishes the page inward to make room for it. Here’s an example where a page goes from needing scrolling to not needing it with the Always setting on:

The scrollbar appears and pushes the page narrower to fit.

This is different than the When scrolling option, in which the scrollbar overlaps the content. Here’s an example of that:

A mousewheel scroll triggers the scroll bar to appear. Mousing over the bar expands the width.

These screenshots are the reason I was thinking about this at all. We had a user write in at CodePen because they couldn’t click that notifications icon. Before I added some extra space to prevent that overlapping, some coverage was possible:

Exacerbated by the fact that this user would zoom out, making the target even smaller, to the point it would be totally consumed:

This is only really a consideration with clickable things hugging the right side of the page. If it’s ever a problem for you, adding some padding over there is likely good enough. Or make the clickable area not confined to that narrow of a target. Here in the WordPress admin, some overlap is possible, but the clickable area is big enough that it doesn’t matter:

Designing for “Show scroll bars” is a post from CSS-Tricks

Source: Designing for “Show scroll bars”

display: flow-root;

News to me! There is a spec for it and Firefox says they intend to ship it. It’s just like display: block; only:

It always establishes a new block formatting context for its contents.

Meaning: you don’t have to use clearfix hacks. There is a bit more to it though. Fiona Chan has a mini-talk all about block formatting context. I think it affects z-index and transforms in some cases too. Anybody?

I suspect Nicole Sullivan will approve. She’s been writing and talking about new formatting contexts forever. In 2010 she even wrote:

I wish we had a simple property value pair that would do the same thing in standards-based browsers.

.lastUnit {
  formatting-context: new; /* please! */

Direct Link to ArticlePermalink

display: flow-root; is a post from CSS-Tricks

Source: display: flow-root;

1 2 3 24