pickpuck

The form/valid one is very interesting but I'm not sure I completely follow, especially the last example. Would you be able to post a Codepen?

These are mostly front-end issues.

Software is often judged based on these UI/UX nuances, but the complexity of building a competent front-end system remains an undervalued part of the process.

The front-end team is usually (1) brought in too late in the game to provide effective feedback and (2) not given enough time to build.

When there's not front-end representation at early design reviews or at initial discussions on how APIs should work, then it's easy to forget things like form error handling.

Designs don't account for all possible states, services/APIs are in flux, until the very end.

Everything else is late, and then all of it has to get slapped together with duct tape and shipped in a few weeks. Performance and browser support be damned.

The article has done the analysis and links to the closest Pantone color "Overcast" and on that page it lists C4C0AA as the hex color.

https://www.pantone.com/color-finder/14-0105-TPG

But you're right -- with a color dropper, I'm getting all kinds of results, typically a darker ~999281.

I wonder how difficult it would be to show the evolution of US jurisprudence via court ruling precedents.

If the only thing being removed were <div> tags, which don't have structural or semantic meaning, it would probably be just as easy to parse for screen readers and robots.

Two problems I see:

1. Where you have a heading you may want it and its associated content wrapped in a <section>. Where you have a separated paragraph you really do probably want a <p>.

So these newlines aren't always just replacing <div>s. The page has no structure except what can be derived from headings.

2. Wrapping everything in a <code> tag seems like it could cause issues. It would probably be better to use <main> and apply the clever one line of CSS mentioned in the post.

> What do we do about this?

https://www.youtube.com/watch?v=DBcz_bGcHgk

After watching this video from Google, I think the future is web components + AOM[1].

This makes sense to me because:

1) Most web developers are already using frameworks (such as React) which can render web components.

2) We can't expect all web developers to be ARIA/WCAG/ADA experts — they're always going to be trying to write code that quickly/efficiently expresses their intent.

Once we get full buy-in and implementation in all browsers and screen readers, most web developers probably won't be using <button> much anymore.

Instead, they'll be using <framework-button>. The <framework-button> sets up all the appropriate ARIA properties/attributes, can restrict what slot content it accepts, and can present remaining issues as errors in the console.

Perhaps under the hood <framework-button> does indeed include a <button> in its Shadow DOM, or maybe it's a <span>.

Coupled with Houdini and some other emerging standards, I think AOM will finally make web components a viable option for most developers, and can solve the vast majority of accessibility issues we see today.

[1]: https://wicg.github.io/aom/explainer.html#motivating-use-cas...

> > The buttons are clickable divs, not actual HTML buttons

> It'd certainly be nice if everything just automagically worked about accessible UI but we're not there yet

OP's suggestion is that the author should have used native HTML <button>, a simple solution that has worked since the beginning.

But you're right that it's not so elegant in reality:

You must remember to add type="button" attribute, otherwise clicking it could trigger page reload accidentally.

Most browsers still force <button> to retain its default display property. Within flowing text, it can never break naturally onto the next line, whereas an <a> link can.

It also can't be a flex or grid container in certain browsers, so you often need an inner element for proper spacing/positioning.

Note that the inner element would need to be a <span> not a <div> because <button> can only contain phrasing elements.

I think what you might be getting at is that having a minority of people with mental disabilities increases the overall diversity of thought within our species, which can sometimes prove beneficial. However, any given mental disability may not be beneficial for the individual.

So one explanation is that natural selection has found a balance that yields benefits for the group.

Nice you can add a <style> tag to your profile!

Please consider making the default colors/fonts CSS variables in the :root so that they can be easily overridden for profile page styling.

The point of the “trending” page wasn’t that it always showed you React. It showed you tiny repositories that had exploded in popularity that day.

My understanding, based mostly on what I’ve seen on Twitter:

911 call -> Dispatch unarmed City employee, typically a social worker, who specializes in the relevant situation, population or neighborhood.

Goal is to assist the individuals involved, to be compassionate instead of punitive, to get to the root cause of the issue.

There is still some kind of armed security backup for the social worker’s protection in situations that do escalate.

I was thinking because it is one of the inks in CMYK for printing.

They are basically paying you a tiny bit to use Edge and Bing with their rewards program. You get points, which can be converted to Microsoft Gift Cards and some other stuff.

Killer features:

* It shows the top comment (It's a bad habit of mine - just reading the comments - so maybe I'll be more likely to click the story instead of the comments)

* Dark mode! Or light mode! Depending on your system settings.

* Easily switch between Top and New stories.

* No JS libraries! (Fast?)

If you’re on an iPhone iOS 13, add it to your home screen. It will open in its own window, not in Safari, so it will maintain scroll state. It also works as a Windows 10 app. Haven't tested on Android...

It's just a 24-hour project I wanted to do over break but I will likely keep it as my main reader, so I might add more features over time.

Based on the data from modern hunter-gatherer populations, it is estimated that at 15, life expectancy was an additional 39 years (total 54), with a 0.60 probability of reaching 15.

https://en.m.wikipedia.org/wiki/Life_expectancy

The idea is that distorting images, logos, or text end up with bad proportions, which the original designer did not intend. Scaling an image of a human wider does not create the illusion of being fat.

(2017)

If remote work became ubiquitous, wouldn’t this be less of an issue? Or would employers just factor in location?

Someone please make a crowdsourced browser extension for news articles that answer clickbait titles, similar to:

https://twitter.com/savedyouaclick

Looks to me like the going price for static templates is $20-$50.

https://themeforest.net/category/static-site-generators https://themeforest.net/category/site-templates https://jekyllthemes.io/premium

> We got permission from our suspect before we released this site and they have allowed to use their name and release the data that we had about them.

Looking forward to your response!

Kudos to you for noticing but! I think they should add some kind of disclosure.

This is native advertising.

But it does have the tone of a type of “data journalism” that we should see more often.

I would appreciate a site that treats all news the way 538 treats politics.

I've been thinking someone with the expertise and influence should write "RDF: The Good Parts"

AKA instead of "Eval is Evil" we might instead say "XML is Evil"

It would be great if you could link to the result. -- The Investigator

Do you have any sources on workplace democracy failures? I would love to read some case studies.

Then to accommodate all users, the perfect lineup sounds like:

* iPhone - iOS (touch only)

* iPad - iOS (touch only)

* iPad Pro - iOS "Plus" (iPad + attachable keyboard/trackpad)

* MacBook - iOS "Plus" (iPad + built-in keyboard/trackpad)

* MacBook Pro - macOS

* iMac - macOS

* Mac Pro - macOS

"Simulacra are copies that depict things that either had no original, or that no longer have an original."

https://en.wikipedia.org/wiki/Simulacra_and_Simulation

Which is better: 1 specification in psuedocode that 4 companies implement unevenly, or 1 codebase that 4 companies contribute to?