Live data from Hacker News

Make Front End Shit Again (2018)

makefrontendshitagain.party

121–130 of 177 posts

Re: Make Front End Shit Again (2018)

#122

Earlier quoted context omitted.

Shouldn't it be possible to still achieve auto-play using JavaScript? It's just a tiny bit more effort. :)

No, the browser checks the call stack of the javascript function. If the play() isn't a direct result of some kind of user interaction. It will just deny you from playing audio. So play upon you open the page is no longer possible. You at least need to wait for the user to touch somewhere on the page.

[deleted]

Re: Make Front End Shit Again (2018)

#123
I wish every site worked like this. Meanwhile I wait for my expensive company notebook to barely handle the 30+ MB of JavaScript Jira downloaded to render a text form which is also completely and utterly broken.

Re: Make Front End Shit Again (2018)

#124
post #33

Earlier quoted context omitted.

I loaded it on mobile too.. - Horizontal scrolling because it isn't properly responsive. - it doesn't reflow when the device orientation changes - no sound (there's an audio control so I guess there's meant to be..) - the audio control sits over the flags - wildly different text sizes everywhere - so much layout shift - from an error loading the Korean version I think it's running on a platform that tracks what users…

Upvote for serious criticism. I still take this over: - the noncompliant cookie warnings - ... with >400 "partners" (yes, I have counted) - works best in IE^HChrome - 20 seconds loading - written for Googlebot, instead of for a human like either the author or me. (Meaning it is bland, formula-driven.) websites I often deal with as long as it provides the answers/entertainment I am looking for.

> with >400 "partners"

You can update the number to 500, as that's what Yahoo has (something like 530, but I don't remember for certain).

Re: Make Front End Shit Again (2018)

#125

Earlier quoted context omitted.

Shouldn't it be possible to still achieve auto-play using JavaScript? It's just a tiny bit more effort. :)

No, the browser checks the call stack of the javascript function. If the play() isn't a direct result of some kind of user interaction. It will just deny you from playing audio. So play upon you open the page is no longer possible. You at least need to wait for the user to touch somewhere on the page.

and now all we need to do is the same for video...

Re: Make Front End Shit Again (2018)

#128

Earlier quoted context omitted.

No, the browser checks the call stack of the javascript function. If the play() isn't a direct result of some kind of user interaction. It will just deny you from playing audio. So play upon you open the page is no longer possible. You at least need to wait for the user to touch somewhere on the page.

and now all we need to do is the same for video...

Video does the same thing, except you can autoplay it if it's muted.

Re: Make Front End Shit Again (2018)

#129
post #24

Drop the annoying music and it's perfect. Beats the "modern" gibberish which requires server grade hardware to be semi-useful(and that is coming from someone who's main computer hasw a dual-socket motherboard with two 14-core xeons filling those sockets).

Every geocities site back in the day had a MIDI file autoplaying on view. This is exactly on point.

Re: Make Front End Shit Again (2018)

#130

Oh shit, you disabled right click? And a rather modern approach for doing it: export default { mounted() { document.addEventListener("contextmenu", event => { event.preventDefault() alert("Right click is disabled!!!") }) } } https://github.com/SaraVieira/make-frontend-shit-again/blob/...

Maybe you know, but it might help someone else. Hold shift when right clicking and it works :D
Post reply on HN