> Elevated Exposure Sites that camouflage their true nature or identity, or that include elements suggesting latent malign intent.
Make Front End Shit Again (2018)
121–130 of 177 posts
Re: Make Front End Shit Again (2018)
#122Earlier 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.
Re: Make Front End Shit Again (2018)
#123Re: Make Front End Shit Again (2018)
#124Earlier 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.
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)
#125Earlier 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.
Re: Make Front End Shit Again (2018)
#126It's a shitty website, but still uses like 500mb of node_modules to build, that's not the way we should be going to.
Re: Make Front End Shit Again (2018)
#127I was a little sad that the inspirational websites portion was empty, other than that, good clean fun...I suppose?
Re: Make Front End Shit Again (2018)
#128Earlier 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...
Re: Make Front End Shit Again (2018)
#129Drop 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).
Re: Make Front End Shit Again (2018)
#130Oh 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/...