potch

9 ms·

31.
by potch 11y ago
Hovering on the graphs in Firefox, nothing happens and the console logs NaN problems.
32.
by potch 11y ago
The low contrast must have impaired your reading ability: > just as the Reactive Manifesto reminded us that new branding can give a youthful glow to decades-old ideas
33.
Peering Through the WebRTC Fog with SocketPeer(hacks.mozilla.org)
3 points by potch 12y ago|1 comments
34.
by potch 12y ago
I do this too- works great and GifBrewery is a nice tradeoff of quality and usability.
35.
by potch 12y ago
Incidentally, you can do this without installing an addon. In about:config, set the `browser.newtab.url` to any URL (file:///, local, or otherwise) you wish. This is really slick- nice work!
36.
by potch 12y ago
Otherwise healthy adults die of the flu every year.
37.
by potch 12y ago
Here's a list of DOM bugs in browsers that jQuery works around: https://docs.google.com/document/d/1LPaPA30bLUB_publLIMF0Rlh... Pretty sure they're not all fixed, and this is just the ignorance du jour.
38.
by potch 12y ago
Yeah! We should find these engineers who might have families and shame them to the world! They'll never work in this town again after they traded in their scruples for a few bucks. In other news, I'm excited to announce my social
39.
by potch 12y ago
Mozilla was the one who decided not to renew.
40.
by potch 12y ago
I will interpret this as a bug report. What browser are you testing in?
41.
by potch 12y ago
This is a project under active development, and was created to address of the need of mobile app developers who expect some form of UI toolkit for building mobile webapps.
42.
by potch 12y ago
Hey, Brick project member here. Completely agreed, the styling for these components is not where it needs to be. We're a small team that works in the open, and like to ship.
43.
by potch 12y ago
22/7 app sux not close enough to pi
44.
by potch 12y ago
I work for Mozilla. I suppose you have evidence I do not.
45.
by potch 12y ago
Yes, we made extra sure this add-on got updated. Lots of TST users at Mozilla :)
46.
by potch 13y ago
I work for Mozilla. I support Brendan as our CEO. I strongly, vehemently oppose his views on gay marriage. I personally won't tolerate any CEO-level chicanery on our internal and external policies of tolerance, though I do not expect a
47.
by potch 13y ago
Engineers aren't just resources to be allocated. Quality isn't a zero-sum game. If a manager said "all of you should only be working on performance", it would be a waste of a lot of people's time who aren't per
48.
by potch 13y ago
This is speculation: The reason Google is moving forward quickly with Shadow DOM implementation is that this polyfill is dog slow . Think about what it takes to make DOM invisible in the browser in a polyfill- overriding every DOM method t
49.
by potch 13y ago
The concern is shipping a non-standard solution and then encouraging developers to use it is the first step toward lock-in. No matter how much you flag something as experimental, it will be used, and the developers who built things using it
50.
by potch 13y ago
I'm suggesting if people in the appropriate working group feel as if a particular solution to a problem (regardless of how old the problem is) wasn't given due consideration, the notion of "speak now or we'll ship anyway
51.
by potch 13y ago
The historical processes boil down to: 1) Single Browser Ideates -> Single Browser Ships -> Time Passes -> Other Browsers Ship -> Standard. This caused delay in implementation and vendor prefix hell. 2) W3C Ideates -> W3C Bik
52.
by potch 13y ago
You're right, the MPAA example is inapt. As regards what makes Shadow DOM special? It's not special. The issue is that Google has made many public claims toward a Brand New Day of participation in standards with Blink. [1] Vendors
53.
by potch 13y ago
Google should respect the desire of other parties to be given adequate time to review their proposals. Being told "you have to object NOW because we're going to ship" doesn't allow third parties to actually identify tech
54.
by potch 13y ago
When the features don't work the same way in every browser, it hurts the platform. Poorly designed features are impossible to take back. (see also AppCache). Web Components is moving quickly, but there has to be an element of care. S
55.
by potch 13y ago
The problem is the standards process exists to keep people from swinging their weight to force rushed/poorly thought-out technologies into a platform some already accuse of fragmentation and bloat. And to people who "But this is G
56.
by potch 13y ago
This article is not actually correct. There are really 2 or three techniques for centering a block level element. The post repeats these techniques for multiple scenarios, and is wrong about the first vertical centering technique.
57.
by potch 13y ago
Sounds like a great spot to set up a hacker commune!
58.
by potch 13y ago
I always wonder where people learned the notion that hypocrisy instantly invalidates any argument in a puff of smug smoke. Yes, Valleywag are pots to the Silicon Valley kettle. It's still funny, and still shines a good light on the idi
59.
High-quality canvas resampling algorithm library(github.com)
5 points by potch 13y ago|0 comments
60.
Data - DOM binding using ES6 Proxies(gist.github.com)
10 points by potch 13y ago|2 comments

More ›