News for hackers. Stuff that matters.
Re:Why it took a long time to build the tiny link preview on... by xab9 on Monday April 23, 2018 @07:28AM (#16902393)
Nope, it's not "done right". It's a table layout from the nineties. But probably there's an api so noone would have to scrape a wiki page, I never needed to do that fortunately :)
Re:Why it took a long time to build the tiny link preview on... by worble on Monday April 23, 2018 @07:50AM (#16902544)
And what exactly is not "done right" about that? If it displays the information it's supposed to in a clean and organised way, and loads as fast as any other website, then I couldn't care less if it's a '90's table layout' or using whatever the hot new JS framework is.
Re:Why it took a long time to build the tiny link preview on... by Nadya on Monday April 23, 2018 @10:31AM (#16903677)
Try to read today's Featured Article in a text-to-speech program. The markup is so mangled it can't even read a complete sentence because it breaks anytime the text links out.
Re:Why it took a long time to build the tiny link preview on... by shakna on Monday April 23, 2018 @05:24PM (#16907555)
JAWS didn't have any issues for me, which reader are you using?
Re:Why it took a long time to build the tiny link preview on... by Nadya on Monday April 23, 2018 @11:02PM (#16909558)
NVDA - aka the "2nd choice" - but I think it may have been a configuration issue on my end as the markup on the page, after looking into why NVDA was struggling with it, is just a <p> with some <a> in it which NVDA should handle fine.
Re:Why it took a long time to build the tiny link preview on... by shakna on Tuesday April 24, 2018 @12:39AM (#16909876)
NVDA can be difficult to configure, for sure. I couldn't get it to play nicely with Sublime, probably my fault. Reason I shelled out for JAWS.
Re:Why it took a long time to build the tiny link preview on... by boomlinde on Tuesday April 24, 2018 @05:45AM (#16911200)
Just taking a quick look at the MacOS article posted earlier in this thread, the whole page uses tables exactly as tables should be used: for tables. How do you suppose tables should be implemented?

I've seen plenty of idiotic examples of tables being implemented with a bunch of styled <div>, probably because people keep parroting the idea that tables are bad because table based layouts are bad.