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

Google Fonts Redesigned

fonts.google.com

Post reply on HN
Print view View original

181–190 of 268 posts

Re: Google Fonts Redesigned

#181

Post by indrora »

donut2d wrote: post #176
cleverjake wrote: post #171

Earlier quoted context omitted.

how so?

I recently ran into this. I was putting an SVG into an tag and sized it with CSS. In every other browser, it worked as expected. The SVG filled the space and stretched to the set dimensions. In EDGE, the SVG appeared tiny at the top-left of the space the took up. I could not figure out a way around it. Had to convert it to a PNG. It seems that it handles SVGs as background images just fine.

I use SVGs all the time in Edge, styled appropriately. Edge however considers (as the spec says) that the bounds of the image are at the bounds of the "page" (as Inkscape sees it, in my experience)

I do The Bad Thing™ with inline styling on occasion, but I've had no problems:

" rel="nofollow">https://zaibatsutel.net/zaibatsu-wide.svg">

Works 100% fine in IE using a layout kit like Marx or Twitter Bootstrap every time.

Re: Google Fonts Redesigned

#182

Post by seang »

Mahn wrote: post #152
irrational wrote: post #134

Earlier quoted context omitted.

At my work we just decided this week that we will no longer support IE or Edge. We won't actively block them (or show a message) and if the site works in those browser then great. But, we won't test in IE or Edge and we won't make any bug fixes just for those browsers. Frankly the number of users using those browsers (low for our site) versus the number of hours required to fix problems with those browsers (high in o…

> I'd be delighted if both IE and Edge went away forever. To be fair Edge is a pretty solid browser these days, I don't think you can put them on the same league. I've been using it for some time now and other than a slightly different font rendering engine I have yet to find a fault on it; everything works like you would expect in a modern browser. Development wise, we test for Edge ocasionally and so far we haven't…

It had some annoying CSS quirks that pissed me off last time I had to deal with compatibility issues.

Re: Google Fonts Redesigned

#183

Post by LoSboccacc »

gizzlon wrote: post #153
hanley wrote: post #84

Earlier quoted context omitted.

I regularly have to email SaaS companies and tell them the service I just signed up doesn't work correctly in Firefox.

I use 85% Firefox and I only see issues on experimental stuff. I'm curious, where do you have these issues?

Firefox is a pain to support. Its box model is slightly different than other browser, like shadows take up space and an outline is rendered around the shadow instead of aroubd the border. There are other minor things especially on the drag&drop events (in same window, not from outside) but I can't recall the specific.

Re: Google Fonts Redesigned

#184

Post by mcbits »

netinstructions wrote: post #45
stonogo wrote: post #32

Earlier quoted context omitted.

Pagination.

I found the non-paginated version to be very responsive and quick. Personally, I prefer non paginated results as long as they're quick, and some user testing studies indicate this as well[1]. UX folks seem to prefer not to paginate[2]. Who loves pagination? Usually advertisers. [1] https://webmasters.googleblog.com/2011/09/view-all-in-search... [2] http://ux.stackexchange.com/questions/21375/is-there-a-point... Codin…

My only complaint with infinite scrolling is that it breaks the scroll bar. It looks like Google accounted for that here by pre-rendering placeholders so the scroll bar doesn't keep resizing and jumping around. (But this wouldn't work so well if they had, say, 10,000 fonts.) Waiting for dynamic content to fill in the placeholders is no worse than waiting for a new page to load.

I just wish we had a standard "lever" widget to replace the scroll bar in lazily loaded pages - similar to the middle-click scrolling on at least some systems that have middle mouse buttons.

Re: Google Fonts Redesigned

#185

Post by jedberg »

Mahn wrote: post #152
irrational wrote: post #134

Earlier quoted context omitted.

At my work we just decided this week that we will no longer support IE or Edge. We won't actively block them (or show a message) and if the site works in those browser then great. But, we won't test in IE or Edge and we won't make any bug fixes just for those browsers. Frankly the number of users using those browsers (low for our site) versus the number of hours required to fix problems with those browsers (high in o…

> I'd be delighted if both IE and Edge went away forever. To be fair Edge is a pretty solid browser these days, I don't think you can put them on the same league. I've been using it for some time now and other than a slightly different font rendering engine I have yet to find a fault on it; everything works like you would expect in a modern browser. Development wise, we test for Edge ocasionally and so far we haven't…

You mean you haven't found any Edge edge cases?

(Sorry I couldn't help myself)

Re: Google Fonts Redesigned

#186

Post by seang »

cickpass_broken wrote: post #129

Todd Motto did a bit of an analysis of the client-side, angular performance: https://mobile.twitter.com/toddmotto/status/7427897282573557... "Google Fonts is doing some amazing work on performance, no ng-repeats - superfast DOM rendering. "

How to make Angular faster: don't use it.

Re: Google Fonts Redesigned

#187

Post by generj »

irrational wrote: post #137
Scarbutt wrote: post #16

Earlier quoted context omitted.

No one tests on firefox anymore, is sad how firefox is being ignored more and more everyday.

In my department every developer uses a different browser as their primary browser. I only use Firefox, another only uses Chrome and another only uses Safari.

That's a very smart way to enforce ad-hoc testing in every browser. Probably prevents a lot of "works on my machine" issues.

I've worked for companies with no defined browser support, and other clients which required us to test in IE6-9, FF, Chrome, Safari, Mac FF, Mac Chrome, Mac Safari. It took FOREVER, so we ended up automating a lot of it.

Re: Google Fonts Redesigned

#189

Post by frenchie4111 »

pimlottc wrote: post #144
stupidcar wrote: post #61

Earlier quoted context omitted.

1. Click a font's plus icon 2. Click on "1 Family Selected" 3. Copy the embed link from the dialog. How is that hard?

Once you know what to do, it's easy, but it's not immediately obvious that you need to "Select" a font in order to use it (as opposed to, say, clicking through to its page), or that clicking on the notification would do anything.

This was my point. It's just not intuitive, and I only use the site once every few months, so I have to figure it out again every time.

Re: Google Fonts Redesigned

#190

Post by DigitalSea »

jeffjose wrote: post #158
cickpass_broken wrote: post #129

Todd Motto did a bit of an analysis of the client-side, angular performance: https://mobile.twitter.com/toddmotto/status/7427897282573557... "Google Fonts is doing some amazing work on performance, no ng-repeats - superfast DOM rendering. "

Is that Angular 1 or Angular 2?

Looks like Angular 1.
Post reply on HN