Tables doesn't work | Sololearn: Learn to code for FREE!

+1

Tables doesn't work

Please help me, the tables doesn't work, watch it below https://code.sololearn.com/WpMw6ZhM29Dp/?ref=app

11/6/2020 3:53:23 PM

AdriFer09

10 Answers

New Answer

+4

The table's working exactly fine. I don't see any problems there. If you're talking about "Why the table doesn't have any borders in it/ not divide with lines?", That'll be because you didn't use any border property. Just write the table like this: <table border="1"(You can use any number as you want)> <tr> <td>Anything</td> <td>Anytihng</td> </tr> </table>

+5

[W3C Response Part 1 of 3] Kode Krasher I'm envisioning a scene where you're in an old silent film, literally standing on a soap box, espousing the virtues and benefits of becoming familiar with the HTML standards based on the authentic source of truth known as W3.org. The crowd begins to grow as more people pass by and gather in to hear your words of wisdom. People start chanting and cheering, "W-3, double-you-three, W-3..." You start screaming (with silent film CC 😉) ... You: "WHAT DO WE WANT?!" Crowd: "H-T-M-L STANDARDS!" You: "WHERE DO WE WANT IT FROM?" Crowd: "W-3" You: "WHO DO WE NOT TRUST?" Crowd: "M-D-N!!" Then... in the background, we see me curious about what's going on... I be like... "Sweet... I likes me a good soap box rally speech about standards... I wonder what he's talking about specifically..." Then it hits me and I'm thinking with a voice two octives lower in slow motion: (silent film CC 🤣) "Whaaaht... daaa... fuuuudge... on a popsicle stick he just say?" 😂🤣

+4

[W3C Response Part 2 of 3] "W3C? w3.org? Mozilla promoting features in their web engine?" Just before you can say another word... I pass you a note which causes you to pause... and then think... "Ruh roh... 😮" --- Okay... I might have gotten carried away with my narrative. Sorry about that. Couldn't resist. 🤓 So... here's the thing, W3C is no longer the official authority for HTML. After years of nerd drama between WHATWG and W3C, WHATWG is now the official HTML Living Standard. Rather than going through a long explanation of this history, I'll provide a set of links in the next post. But first, before I forget, regarding MDN, while there might be features specific to Mozilla, MDN covers browser specific features for all the major vendors... AFAIK. MDN is one of the most reliable, transparent, and inclusive of all the sources on implementing the web standards for all browsers. Another good source is https://caniuse.com. Okay... so... I'll post links regarding WHATWG and W3C next.

+4

[W3C Response Part 3 of 3] I've reviewed each of these links and believe they each hold information that should be relevant to fast track the details about this history: ---- First... let's start with a word from W3C: https://www.w3.org/html/ ---- Live the challenges from the confusion as they unfolded in this Q&A Post: https://stackoverflow.com/questions/6825713/html5-w3c-vs-whatwg-which-gives-the-most-authoritative-spec - Read all of it from the 2011 posts to the update titled, "2019: The war is finally over" and comments throughout. ---- A summary of it all: https://medium.com/swlh/w3c-whatwg-standards-437b375cb793 ---- A little about WHATWG from them directly: https://whatwg.org/faq ---- The official HTML Living Standards: https://html.spec.whatwg.org/multipage/ ---- I hope this was all helpful.

+3

AdriFer09 I completely agree with Martin Taylor ... unlearn using border=1 as that is a discouraged legacy attribute prior to HTML5. Tanmoy Kumar Hopefully, you will also learn this if you weren't aware before. 👌 I recommend reviewing the deprecated attributes for future reference. https://developer.mozilla.org/en-US/docs/Web/HTML/Element/table

+2

This might be a place to pull out my soap box? 🤔... if you are going to spend the time learning new tags, you might as well make sure you search the official living HTML documentation to see if what you are using is obsolete: https://dev.w3.org/html5/pf-summary/obsolete.html while SL is promoting HTML5, I doubt any browser will ever require HTML5 ONLY syntax anytime soon. But the concept here is to use best practices, and use the current standards. I also would add that while Mozilla is a good resource, make sure you scroll down to the bottom of the pages and understand browser compatibility of features you are researching. Don't think everything on their site is HTML standard, because it is NOT... some of their content does not work cross platform and are simply Mozilla add-ons promoting features in their web engine. Likewise, you will find old and misinformation all over the web, so validate your sources, along with your audience and the browsers they might be using... and Happy Coding! 😎👍

+2

David Carroll /me steps off soap box and goes home. :blackeye: After looking at some of my bookmarks, I realize now they actually link to whatwg.org... I guess it is a good point to pay attention to news releases and not just bookmarked ref pages? 🙄 I use MDN (after you and a few others pointed me in that direction)... BUT I get frustrated with omissions that leave folks using apple products wondering why methods and certain features do not work. Alternatives exist, but unless you know them, searching for them can be a challenge. I mentioned scrolling down the page because of caniuse.com and compatibility charts, which are a must for those wanting to verify cross-platform compatibility. Usually, leading to "x equivalent on apple" searches, that eventually get me where I need to read...Hitting loads of old or misleading articles along the way. Thank you for your insight again! Not in total agreement with your feelings on MDN, but it is a useful resource, and I am grateful for it most days. 😉👍

+2

Kode Krasher Regarding your frustration about information that isn't consistent with Apple products, I'd need to see specific examples of what you're referring to. But... my gut tells me it's less about outdated or misleading articles and more about Apple being slow to update or investing in their browser consistently across platforms. I do recall a few times where we've hit a bump in the road with some bug related to Safari only to see the subtle discrepancy documented in MDN. It's tough trying to keep up with all the browsers from a documentation standpoint and I'm sure MDN will not be perfect 100% of the time. But... I'm hard pressed to find any examples. Please do DM me with examples and I'd be happy to take an objective look on a case by case basis.

+1

Thanks, no it works