Live data from Hacker News

Firefox 39.0 released

mozilla.org

31–40 of 105 posts

Re: Firefox 39.0 released

#31
post #22

Earlier quoted context omitted.

This is bullshit.

How so? If you're white, perhaps you see no problem with making everyone's skin white. But the billions of people who aren't white might have a problem with it.

Emojis are used for communicating emotion, not skin color. If the user want them to be displayed black (or even replace them with cat and dog faces) it should be up to them, it's just a user preference.

Re: Firefox 39.0 released

#32
post #3

How much does Project Silk improves scrolling performance? Can you "feel" it? Scrolling/motion performance is the only thing that is keeping me away from FF at the moment - Even dev tools are getting amazingly good.

I can't feel any difference between Chrome and Firefox when scrolling, but http://www.vsynctester.com/ is jankier on Firefox on my old-ish Macbook Air.

Re: Firefox 39.0 released

#33
post #18

So, they finally fixed Logjam, 1 month and a half after publication. Chrome still hasn't fixed it. Color me unimpressed.

Since Chromium is open source, you can contribute to the project. I'm sure if you send a quality patch to the Chromium dev team to fix Logjam, they'd be willing to review it.

Did you try to contribute to Chromium and Firefox to speed up fixing the Logjam issue ?

Re: Firefox 39.0 released

#34
post #11

> Disable use of RC4 except for temporarily whitelisted hosts This is the one which has the greatest chance of giving people a headache. For instance, one of the biggest banks here still uses only RC4 for its online banking site. Its top-level hostname and a few of its auxiliary hostnames are on the whitelist, but there's no guarantee that all the RC4-only auxiliary hostnames it might use for some of its functionalit…

Good. Breaking their websites is the only way some people will fix their broken security.

Re: Firefox 39.0 released

#35
post #11

> Disable use of RC4 except for temporarily whitelisted hosts This is the one which has the greatest chance of giving people a headache. For instance, one of the biggest banks here still uses only RC4 for its online banking site. Its top-level hostname and a few of its auxiliary hostnames are on the whitelist, but there's no guarantee that all the RC4-only auxiliary hostnames it might use for some of its functionalit…

Good. Breaking their websites is the only way some people will fix their broken security.

YES. Force them to upgrade their weak sites!

Re: Firefox 39.0 released

#36
The preconnect relationship is intriguing; I hadn't been following the adoption of resource hints.

Sidenote: I find it really interesting that the current spec suggests preconnect and its siblings accept a probability attribute estimating how likely connecting to different resources is.[1] Something funny to me about making the directed-graph/state-machine nature of the internet finally show through the markup.

[1] http://www.w3.org/TR/resource-hints/#hint-probability

Re: Firefox 39.0 released

#37
post #22

Earlier quoted context omitted.

This is bullshit.

How so? If you're white, perhaps you see no problem with making everyone's skin white. But the billions of people who aren't white might have a problem with it.

> How so? If you're white, perhaps you see no problem with making everyone's skin white.

> But the billions of people who aren't white might have a problem with it.

I'm not white, and I have a problem with "skin tone" emoji.

Previously, skin tones for emoji were left up to the font creator. In practice, this meant that they were usually lime green, neon blue, or Simpsons yellow, all of which are cartoonish enough not to be evocative of any particular real-life skintone.

I can't really imagine a situation in which drawing attention to the race of an emoji character is desirable or even acceptable. I'm sure some exist, but they're nowhere near important enough to be included in the actual standard itself.

Beyond that, the skin tones used are incredibly reductive. Human skin tones are not as simple as 6 different shades of brown. (I, for one, cannot match my skin tone to any of the examples on the Unicode website). And if we want to get philosophical, there are a number of ways in which race and culture are encoded (literally) into emoji that are far more subtle, yet more significant, than the color used to render the skin of the faces. In a way, it reminds me of the picture-interpretation tests that they used to administer at Ellis Island to "prove" that certain immigrants were not "fit" for life in the US, though that's perhaps a topic for another day.

Re: Firefox 39.0 released

#38
post #22

Earlier quoted context omitted.

This is bullshit.

How so? If you're white, perhaps you see no problem with making everyone's skin white. But the billions of people who aren't white might have a problem with it.

Billions of people who aren't white were using and invented emoji before white people even got to them.

Re: Firefox 39.0 released

#39
post #22

Earlier quoted context omitted.

This is bullshit.

How so? If you're white, perhaps you see no problem with making everyone's skin white. But the billions of people who aren't white might have a problem with it.

I have never thought of emoji as having any particular skin colour, until this recent trend to make skin colour selectable.

Emoticons and emoji have traditionally been displayed as yellow cirlces with large faces. White emojis have been the exception, not the rule. I have never had a problem with being represented by a character with Jaundice (a medical condition turning your skin yellow).

Re: Firefox 39.0 released

#40

And yet there are still issues on my Sandy Bridge system with display corruption even with the latest Intel drivers. Also has anyone else noticed that Firefox is no longer keeping the page state when navigating back? For example on Reddit go to the comments section, minimize a few comments then navigate to a link then go back and none of the minimized comments remain minimized, in Firefox prior to 38 things worked co…

I haven't seen many people mentioning this problem before. I've seen it come up in discussions on the current AMD GPU lines. Hard to say who is to blame, but it's rarely obvious just how many problems there are before buying a card. I got a cheap R7 260x which seems to have trouble with waking up from low power states. Some people even made custom BIOS's to fight the problem.

I don't know how more modern stuff like accelerated transforms, canvas, WebGL or DirectWrite play into that equation. Browsing seems to pull out GPU's from the lowest power modes constantly, which might cause these problems on a wide variety of GPUs.

Post reply on HN