msujaws

This conversation happened online, so I'm not sure this is technically against the law.

I am the project mentor for the Google Summer of Code project to implement multi-select tabs.

See the bottom of the table at https://wiki.mozilla.org/Community:SummerOfCode18 for more info and please apply if you want to see this added to Firefox! :)

Employer-provided healthcare is considered compensation, and the "cost" is somewhat determined at will depending on creative accounting.

As long as Debian is altering the binaries this clause does not apply.

How did you get 5.4 things fixed per day? They said over 10,000 issues fixed in six months.

10,000 / 182 = 54.94. It looks like you had a decimal error.

It looks like some of the user experience ideas from Google Messenger have made their way to Google Hangouts. How long does Google plan on supporting two Android SMS/MMS apps?

I've been using Messenger and it's pretty nice. I especially like the ability to search through my messages, something that the Hangouts v4 screenshot doesn't show.

Note, click-to-copy will eventually not need Flash :)

See https://groups.google.com/forum/#!topic/mozilla.dev.platform...

This would be useful if you were making UI components and you want a generic wrapper element to contain say a checkbox and a label. The wrapper can have display:contents, allowing the checkbox and label to have a shared parent for movement through the DOM or selection via JS, but otherwise have no styles that apply to their parent.

You should go to about:support and use Refresh Firefox which will probably fix most of your crashes (outside of Flash-related ones which should only be affecting the plugin and not the browser).

Add-ons can be distributed outside of AMO. A secondary (more scary) dialog is shown before the add-on can be installed, but users can click past it to get to the add-on.

PDF.js uses this approach actually. See "Development version" at https://github.com/mozilla/pdf.js/ as an example.

Pure linkbait. There is nothing in the article that causes any issue with open source.

While the review may have been delayed, all points described by the review are reasonable and have no relation to open-source. The root problem is the slow turn-around time, but writing an article that attacks the volunteers who are doing the reviews is pretty mean spirited. It would have been a lot easier to join #amo-editors, #amo, or #addons on irc.mozilla.org and ask for help there.

To point out a couple flaws with the post: 1. "Worst of all, many Ember.js developers who prefer Firefox have accused us of treating it like a second-class citizen, since they assume the month+ delays are our doing." --- If it's not treated as a second-class citizen, why was an Ember.js Chrome extension written by the team but the Firefox one was deferred to someone outside of the core team?

2. The SDK being out of date is flagged during upload. Add-on authors can still request hand-review, but it's obvious immediately that it won't pass review.

Except a team of Googlers doesn't "bless" add-ons. They may have some automated scripts, but it is pretty easy to add code to your add-on that does things that your add-on was not advertised to do (malicious or not).

As a front-end engineer who works on desktop Firefox for Mozilla, I think we have actually held to your "no major redesigns more than once every 2 years" request ;)

Australis was a UI change that we don't anticipate doing more than once every two years. We recognize the costs of doing so, for users, add-on devs, and Mozilla devs.

I filed https://bugzilla.mozilla.org/show_bug.cgi?id=1071067 to get this issue tracked. I agree that we could do a better job here, as the unfolded view takes up 3x the vertical space compared to the inline view.

In fact, (2) is not as true as it used to be. This graph, http://cdn.arstechnica.net/wp-content/uploads/2014/07/chrome..., shows that about 6-7 percent of worldwide browsers are out-of-date Chrome installs, and the trend is for that to grow.

From http://arstechnica.com/information-technology/2014/07/window...

There is a space following one of the slashes.

Why drone valley and not autonomous vehicle valley? Seems more prime for the motor city.

Not to mention, Detroit already has some large neighborhoods that are mostly vacant and the roads could be shifted over to test grounds for the autonomous vehicles. Michigan endures extremes in all four seasons, as compared to Santa Clara County which has pretty moderate weather year round.

But I don't think Marc was specifically saying that Detroit is for drones. I think that was merely an alliteration. I do think Marc is right in that specialization is the key.

Most likely not a PR stunt gone wrong, but a pricing error on the website. Those who ordered will probably get an email stating that their order has been canceled and they'll be refunded their money.

The UI of Firefox is actually drawn using all web technologies.

The tabs were completely rewritten when changing the styling. The old tabs used a border that was drawn along the edges, which turns out to be quite expensive. Another expensive implementation detail in the old tab shape was a subtle linear gradient. The border and gradient are computed each time that they are drawn, whereas the new tab design uses a combination of background-images and SVG clip-paths (the clip-paths are used to get mouse events to follow the curved shape of the tab).

This blog post covers just one of the many performance tests that we ran while working on the version of Firefox. We also tracked other key metrics such as new window creation and the amount of time to enter/exit customization mode.

Very cool, I like the Console to Inspector hookup that they added!