161–170 of 187 posts
Earlier quoted context omitted.
All major screenreaders work from the DOM and the accessibility tree nowadays, and have done for a long time at this point. Dynamic content is no problem in and of itself.
Unless you are fetching data async. Google and other will not wait for data.
Earlier quoted context omitted.
While I totally agree about this site, it's stupid to disregard JS as a whole. Imagine websites like FB without JS - it would be horrible.
You don't have to imagine, you can try: https://mbasic.facebook.com/ - a lot of people prefer it to the standard monstrosity.
Earlier quoted context omitted.
That's not an equivalent analogy. Disabling JS displays nothing at all , while changing text and background color is a progressive enhancement. Content should still be accessible without JavaScript, even if, perhaps, in a less convenient way, i.e., every click reloads the entire page
But why? Who made the rule that websites should work without JS? Content being accessible without JS is best practice. I get it and it was very valuable a long time ago. It comes in handy sometimes today but for most of the internet accessing world, working without JS is not a requirement. I do not get why people ding products for not working when JS is not enabled.
Please pardon my negativity but i'm tired of this trend of taking something that span discussion on HN and making it into an app as soon as possible, then posting it on HN. It's getting out of control since the old geek jobs article on Indiehackers. There's now at least one of these posts per week and they're less and less interesting. It's not showing cool tech or a cool idea, it's just trying to capitalize on the i…
Sorry, but I am going to comment on a technical implementation rather than the content of a site. The site shows blank page without JS enabled. I did not understand why one would need one megabyte of minified Javascript to display a list of 10 items. Probably it is because the developers were too busy learning trendy JS frameworks and do not know about HTML and server side page generation (in PHP this could be done m…
> The site shows blank page without JS enabled. I did not understand why one would need one megabyte of minified Javascript to display a list of 10 items. It's probably because you opted to disable one of the essential web technologies in your browser. Plenty of websites are written as SPAs nowadays. This is like complaining that pages are black on white because you disabled CSS. Or that you can't see websites at all…
Earlier quoted context omitted.
Unless you are fetching data async. Google and other will not wait for data.
That's not true. Google indeed waits for async content to load for a given amount of time. You can inspect this from the Google webmaster tools.
Sorry, but I am going to comment on a technical implementation rather than the content of a site. The site shows blank page without JS enabled. I did not understand why one would need one megabyte of minified Javascript to display a list of 10 items. Probably it is because the developers were too busy learning trendy JS frameworks and do not know about HTML and server side page generation (in PHP this could be done m…
Earlier quoted context omitted.
That's not true. Google indeed waits for async content to load for a given amount of time. You can inspect this from the Google webmaster tools.
I did a lot of tests on this and Google just didn't wait, no matter the configuration. I tested using webmaster tools. The App was built using React, and I ended up implementing SSR to fix the problem. There are a lot of posts that hack this embedding JSON directly on the page. I didn't find any post that figured out a way to make this works through async API requests. I would thank you if you point one in that direc…
I've bookmarked this site: "Testing a React-driven website’s SEO using “Fetch as Google" https://medium.freecodecamp.com/using-fetch-as-google-for-se...
That talks about this. Not had a chance to verify this. just a fyi.
Earlier quoted context omitted.
I did a lot of tests on this and Google just didn't wait, no matter the configuration. I tested using webmaster tools. The App was built using React, and I ended up implementing SSR to fix the problem. There are a lot of posts that hack this embedding JSON directly on the page. I didn't find any post that figured out a way to make this works through async API requests. I would thank you if you point one in that direc…
Were you using react-router by any chance? I've bookmarked this site: "Testing a React-driven website’s SEO using “Fetch as Google" https://medium.freecodecamp.com/using-fetch-as-google-for-se... That talks about this. Not had a chance to verify this. just a fyi.