Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Firefox 36.0 released

mozilla.org

Post reply on HN
Print view View original

221–230 of 256 posts

Re: Firefox 36.0 released

#221

Post by Silhouette »

pmontra wrote: post #101
jherdman wrote: post #61

I'm presently in the middle of an experiment to use Firefox (and its Developer Edition) as my primary browser when performing my duties as a web developer. So far... It's been kind of rocky. Daily usage of the browser isn't that bad, but the developer tools are lacking compared to Chrome. A good example is the Network tab. In Chrome, I need only have the developer tools open to capture information about requests. In…

You should install Firebug. It's better than the integrated dev tools in almost all areas. About writing extensions we had this on HN in September 2014 https://news.ycombinator.com/item?id=8285744

You should install Firebug. It's better than the integrated dev tools in almost all areas.

Really? I uninstalled Firebug not so long ago, having concluded that it offered little added value any more, while measurably, repeatably, and dramatically reducing Firefox's performance. Has either or both of these things changed in the last few months?

Re: Firefox 36.0 released

#222

Post by shmerl »

laumars wrote: post #219
shmerl wrote: post #194

Earlier quoted context omitted.

On Debian defaults are all under /etc/fonts About general idea of what all those settings are, here is a brief overview: https://en.wikipedia.org/wiki/Font_rasterization FontConfig rules can even be applied to Web fonts, which at times can be messed up by default. Example of such rule for fixing some mess on DuckDuckGo: @font-face:DDG_ProximaNova true lcddefault The difference it made for me (note the word Wikipedia…

I didn't know this worked against web fonts as well. Is there any chance you could share your webfonts config in its entirety? Maybe post it on github or some whee? I'd be hugely grateful :)

That's really the only such setting that I have :) I use DuckDuckGo as my primary search engine and that messed up i was irritating me a lot, so I was digging for a way to improve the look of Web fonts and discovered that Fontconfig can affect them.

Re: Firefox 36.0 released

#223

Post by [deleted] »

neokya wrote: post #163

Recently switched back to Firefox. Their search engine selection option is so easy and excellent. On Chrome, non-technical people won't be able to change default search engine. Thanks Mozilla.

[deleted]

Re: Firefox 36.0 released

#225

Post by etimberg »

hamitron wrote: post #214
hamitron wrote: post #131

I just updated and it broke my selenium scripts.

thanks for the downvotes, but I've literally spent all day trying to fix my QA environment after updating to firefox 36.

It seems to be a known issue with Selenium 2.44. Hopefully it gets fixed ASAP

Re: Firefox 36.0 released

#228

Post by jekrb »

Curmudgel wrote: post #224
agumonkey wrote: post #20

Meanwhile, in firefox 39a (current nightly), a reader view (readability/printfriendly) http://imgur.com/DONqb30

It's a shame that the "readable" mode has #333 body text instead of #000.

#000 needs to be used tastefully, otherwise it can be visually overbearing.

Re: Firefox 36.0 released

#229

Post by arvinsim »

pmontra wrote: post #101
jherdman wrote: post #61

I'm presently in the middle of an experiment to use Firefox (and its Developer Edition) as my primary browser when performing my duties as a web developer. So far... It's been kind of rocky. Daily usage of the browser isn't that bad, but the developer tools are lacking compared to Chrome. A good example is the Network tab. In Chrome, I need only have the developer tools open to capture information about requests. In…

You should install Firebug. It's better than the integrated dev tools in almost all areas. About writing extensions we had this on HN in September 2014 https://news.ycombinator.com/item?id=8285744

The only thing that irks me is that there is no native dark theme for it.

Re: Firefox 36.0 released

#230

Post by Curmudgel »

willlma wrote: post #227
Curmudgel wrote: post #224

Earlier quoted context omitted.

It's a shame that the "readable" mode has #333 body text instead of #000.

http://ianstormtaylor.com/design-tip-never-use-black/

That is poor advice which doesn't account for the difference between computer screens and ink on paper. The deepest black you can get on a monitor will not be as dark as certain inks on a page.
Post reply on HN