philipwalton / blog Goto Github PK

Hi, I am new to Web development. I read you artical Page Lifecycle API | Web | Google Developers, it helps a lot. I have a little confusion:
In the unload event section, you say:

If you need to support Internet Explorer versions 10 and lower, you should feature detect the pagehide event and only use unload if the browser doesn't support pagehide:

and you use the code below:

const terminationEvent = 'onpagehide' in self ? 'pagehide' : 'unload';

I test the code in my project, it seems if we want suprot ie10 and lower, the const can't be supported according to const - Javascirpt | MDN, may be we should use var? I use var successfully in my project.

And I have another problem, if my project don't need to supprot moblie, will using unload directly cause some problems?
Sorry for my poor English. Wish I can be understood. Thanks.

This is what a paragraph looks like on my latest Chrome on a non-retina MacBook 13':

This is what it should look like:

On my machine the font-size: 1.0625em converts to 17px. The line-height: 1.47 converts to 24.99px. The text bounding-box for each row is 20px. I don't know how thats calculated. I thought like 17 + (24.99 - 17) / 2 but that results in 20.995 – does it round down? Never the less – the gradient underline background is positioned at 0 1.25em which results in 0 21.25px. Since thats outside the text bounding box of 20px the underline doesn't render. 0 1.17em is the first value that goes below 20px (19.89px) and makes the underline visible.

https://developers.google.com/analytics/devguides/collection/gajs/eventTrackerGuide

When I tried adding the JavaScript tag to a post, it appeared at the bottom of the list in the sidebar, out of alphabetical order.

Google is detecting duplicated titles because it's considering /articles/ and /articles to be separate pages.

Tags like CSS and HTML that want to be uppercase cause problems. The URLs for them should be lowercase but they should appear as authored in all other situations. Currently the tag index pages are not finding their posts.

Some Chrome extensions (e.g. Ghostery) seem to block Typekit in a way that the current error handling doesn't account for.

More details:
https://twitter.com/jblanchefr/status/503885716997537793

Context: https://twitter.com/teddyzetterlund/status/812170698911318020

Currently the tweet link hangs off the right side at really small widths.

The JS-swap-in page navigation is fast and cool, but right-clicking/Ctrl+clicking to open links in new tabs fires the navigation also.

Not sure about touch, but that might be an issue too.

tested in Firefox and Thunderbird

When I revisited the "Deploying ES2015+ Code in Production Today" article, I was surprised to see it had been updated (inline) to change main.js to main.mjs.

Given that this article has been linked from many sites as "the resource" for how to deploy ES2015+ code (e.g. here), I would suggest explicitly noting that the article has been updated and that the original version of the post didn't use the .mjs convention.

Additionally, .mjs still has some caveats: it requires you to explicitly set the correct Content-Type (because it won't happen automatically, like it does for .js, on many popular web servers) and it doesn't generate sourcemaps in webpack (webpack/webpack#7927). Beginners that come to the post are likely to get tripped up by these issues, and they would have avoided them if they read the original version of the post instead. So, I would also suggest clearly calling these issues out. You could perhaps link out to "A note on file extensions" and that webpack issue.

This link is broken. Cant access in ur blog