02Geek HTML5 and JavaScript, TypeScript, React, Flash, ActionScript online School
Previous VideoNext Video

Changed elements and attributes

It would be impossible to list out every change as its still changing. html5 is a very much live and changing document as of early 2012. Its not impotent to memorize what is changing but understanding why the changes are happening. as if you know why the changes are happening it will make it really easy to remember what is part of the new and what shouldn't be used anymore.

Video Transcript

00:00Now, the next topic is about changed elements, and actually there are a lot of changed elements,
00:05and there's a few rules to these changes.
00:07Now, it's impossible to really go over in a course that's going to be an hour and a
00:11half or two hours and actually list out every single element, but it's also a waste of your
00:15time because I think this is a document that's changing.
00:19A lot of it you could actually even get to, and I'm going to just open this up because
00:22I have this next to me right here, so I'm going to just open this up quickly.
00:25I have this list of changes, basically w3c.org, and I'll put the link up, which HTML5
00:31differences from four to five, and it just lists out all the different changes.
00:34Now, obviously, this document is changing and morphing over time, so it's going to
00:40change over time still, so it's not as important to remember by heart what elements
00:44change, more to understand why are they changing, and the why is not going to change
00:48more than the what exactly is changing.
00:50So, for example, stuff that are being removed or change our address, so there's
00:58quite a lot. So, for example, the address, which is now basically they just change
01:02the scope of address. No one really uses address, but now they'll probably use it
01:06more often, so there's actually an attribute that was there. I haven't actually seen
01:09anyone actually use it, but now instead of it being something visual, it's going
01:13to be actually just something that represents content. Same deal for B, so B has
01:18changed. Technically, B is still there, but instead of B being for the
01:24purpose of making something bold, B is now for a different purpose. Now it
01:27represents a span of text that actually we're calling attention towards.
01:32Now, it could be for a lot of different usages, but basically we want to call
01:35more attention to it. It's an important element inside of our document, so not
01:39necessarily bold. It might be in a different color. It's our decision,
01:42because we're going to do it in CSS. So, it's really about changing the, and that
01:46goes through every single one of these. If I run through this quickly, so site is
01:50now, if you want to quote from someone else, or you want to quote actually a name
01:54of a book, or a name of an essay, or a name of the reference that
01:58you're getting something from. So, that will be sites. Instead of it
02:01actually changing something visual, that's its goal. HR
02:06Element that used to just create a line on the stage, basically HTML5 said as
02:10well, instead of that, use that as a break between paragraphs, a
02:15thematic break between paragraphs. I used to be just to be indenting things, I think
02:19was called, or to make things italic. So now, and now instead of it being just
02:24italic, it's about representing a different mood in a conversation. So, for
02:29example, if you go to acting, for example, so if you have a script of
02:34acting, so maybe you would set it as I, the parts where someone is
02:38talking, and versus the narratives of explaining where you are, will just be
02:41regular text. So the idea behind it is not as it's not a big shift from what it
02:46was. And I'm not going to go on every single one in the list, because you could
02:49find them in that document that I was talking about. But all these changes,
02:52really, all the changes to all the elements are basically taking things that
02:55were visual. And basically saying, okay, from now on, they're not visual,
02:59they're a thematic idea. Now, you can make it still italic by going in your
03:02CSS. And by the way, browsers are still going to make be bold forever. That's
03:07that's because, like we said in our first video, that they're the rules for
03:11us, the people of Earth. And then there's the rules for the browsers. So for the
03:16rules of the browsers, whenever they see B, they're still going to make it B
03:18because they have to support HTML, 432, and so on. So basically, although the
03:24rule for us says, well, don't use B just to make stuff bold, make use B to make
03:29stuff to emphasize or to make sure that this is an important element in
03:33this text that you're reading. Don't use
03:36the style sheet I can make B green. It doesn't have to necessarily be bold.
03:41Exactly. Exactly. So it's kind of like taking away that, that exact meaning of
03:47what B was and turning it into being something more theoretical. And then it's
03:50kind of like in your hands to decide how exactly you want to translate what B
03:54is actually going to look like. But thematically, it's
04:00it's becoming an item rather than a
04:02exactly. It's kind of like the new header elements and the footer elements
04:06that they that they don't change anything visually. But they're in charge
04:10of representing a type of information. And really, that's the goal of HTML
04:14five of making sure that all the nodes that exist, all the elements that
04:17exist, represent something, they're not just there for visual aesthetics,
04:21because if they're there just for visual aesthetics, then put in CSS,
04:25there's no reason for it to be inside of HTML anymore. So for example,
04:30it we're going to get into the deprecated nodes. And as we said,
04:32there's no such thing as deprecated because the browsers are going to
04:34support it no matter what. But when we look at the stuff that HTML five
04:38says, well, don't use it anymore, we're going to see that those are
04:41related to things that just don't have any meaning besides visuals,
04:45such as the font, which they don't have any meaning on their own
04:47besides saying change this font. Okay, so whatever HTML five consortium
04:53whatever they couldn't figure out, I guess, to find it a real reason,
04:57a real usage, they just got rid of it. But the browsers still have
05:01to maintain it and support it. Alright, so let's see the next the
05:04next element. Let's look at change attributes. Now, obviously,
05:07again, change attributes is actually a very long list. And
05:11it's changing. So excuse me, change after we're not going to
05:14get into every single attribute, we're just going to look at a
05:16few rules here. Like we saw in our first videos, type is not
05:21needed anymore for style and script, because we have already
05:23one type, that is our standard, the ECMA script, the emca script,
05:27which is JavaScript, and we have our CSS or style sheet. And
05:31there's no need to describe what they are, because we already
05:33know what they are unless we're going to use something else, and
05:35only then we would use the type. So it's not necessarily
05:38deprecated, but just not needed anymore. Visual attributes in
05:42general, so anything that changes visuals think things such as
05:45let's say, the body used to have an attribute of
05:48background, or bg color, done, gone, not supposed to use it
05:52anymore. You'll you still could, but you're not going to
05:55comply to the way that the visionaries of HTML5 wanted it
05:58to look like. Alright, so that's about that about that
06:04topic. Now, language attribute on script is not needed
06:07anymore. Same deal as before, we already know what language
06:09is, there's really no purpose for it anymore. Name on an a
06:12tag was just an overkill, because people were just using
06:15the ID. So instead of using name, use ID, everyone's using
06:18it anyways, that way, there's no need for a name, because
06:21it doesn't add an extra value, ID is more useful. With and
06:25hide on images should not be in percentages anymore. I don't
06:28know why it shouldn't be any percentage anymore. But that's
06:31one of the decisions of of the consortium. But basically, a lot
06:35of it is also because when you put an image, that you
06:37really shouldn't be scaling images, because it just ruins
06:41the quality. And then you're just putting something that
06:43doesn't look that good, do any any image manipulation in
06:47CSS and not directly on the stage. And that's probably one
06:49of the reasons why they're getting rid of that
06:52percentage. All right, now, let's look at the next
06:57category of elements. So the next category, I'm grouping it
07:00up together are absent or removed elements and removed
07:03attributes. And again, not going through every single one
07:05of them, because we understand the thematic idea behind
07:08them. So I'm just going to group them up into thematic
07:10ideas. So visual elements, anything that is in charge of
07:13changing things visually, but has no other purpose besides
07:17that, such as base font, big center font, all those
07:20stuff are deprecated or removed or ignored in favor of
07:24CSS. Now, that's unfortunately for me, because I love
07:27sender, it's so easy to work with, but they don't want
07:30me to work with it anymore. But I'll probably work with
07:32it still once in a while, because I know the browser is
07:33going to support it. So unless I'm in the CSS mode,
07:37I'm probably just going to use that sender, although
07:39I'm not supposed to frame frames that no frames really
07:44is deprecated for the main reason, because no one is
07:46using it. And also because it just doesn't it doesn't
07:49work that well, just never really performed well, it
07:52creates usability issues, it creates just tremendous
07:55amount of unhappy people. So if frames are still
08:00supported, but anything related to frames and frame
08:03sensor just has just been removed. Acronym has been
08:06removed mainly because people don't didn't really get
08:08what it was. Although it is a thematic idea, it's
08:10been removed in favor of ABBR, which was
08:13abbreviation, people didn't really understand why
08:15would they use an acronym or abbreviation would seem
08:18kind of like the same thing. HTML4 seemed to think
08:21that it had a real usage. But the reality was people
08:24weren't using acronym, and we're getting confused
08:26between the two. So HTML5 said, okay, just use ABBR,
08:30there's no need for both of them. Applet has not
08:33been used in ages, which was really a way of
08:36retrieving third party plugins. And it's been
08:40deprecated in favor of object to be used for
08:43third party plugins, which is basically reality,
08:46everyone's using object, no one's really using
08:48applet. Presentational attributes, same deal. So we
08:52talked about visual elements. So anything that's
08:54presentational has been removed. So if I if I
08:57scroll into their document for a second to find
08:59something that represents that BG color, all right,
09:04because there's no there's it's an attribute
09:05that's not needed both for the table, both for
09:07the body, both for basically any place that
09:09there's a BG color, or background, or a line, or
09:14size, or type, all these stuff, all these stuff
09:18are really just related to visual aesthetics and
09:20anything related to visual aesthetics. Basically,
09:22the rule is don't use. Okay, does that make
09:24sense?
09:26It does. It does. I have a maybe off topic
09:30question, but I do a lot of e-blasts, and I
09:33have to use in line style. Now would you say
09:39I don't think so. I think like, you know, emails
09:44has been one of the most prehistoric types of
09:47way of building you actually are not even
09:49supposed to use any CSS and emails, just to
09:52support backward compatibility, you're still
09:55going to be working in HTML for because you
09:57have to use visuals for that. And that's kind
09:59of probably one of the reasons why they're not,
10:01you know, saying don't use it at all. You're
10:03just not going to use HTML five for email
10:05blast. Right. Okay. Because you're still
10:07going to use tables, right? Yeah, yeah. So it
10:13really is still a separate thing. Okay. Yeah.
10:15And I don't see it changing. You know why?
10:17Because like, well, it might change in the
10:19future, but there's just still a lot of
10:23contrary to mobile devices, which are more
10:26ready for it. I think there's a lot of
10:27older, older operating systems that work on
10:31emails. And I don't know, it's a standard
10:34already. And I know that maybe it will
10:36change. But for now, no one's really
10:37talking about it. I think also a lot of
10:40it also has to do with the fact that
10:42loading is loading in external files in
10:45an email is more dangerous. It's more
10:47problematic. You know, you want to, you
10:49want to contain everything you have
10:51inside of your email and kind of avoid
10:52adding extra, you know, like, um, dependent
10:55on the user's machine. Yeah. And I think
10:59that that's, that's an email program to
11:01accept things. And with all those controls,
11:04it's just too difficult. So let's just
11:06put that to the side then. I think that
11:08that will stay the way it is for quite
11:10a while. I think so. Yeah, I think so.

Ready to Level Up Your Skills?

Join thousands of learners on 02GEEK and start your journey to becoming a coding expert today!

Enroll Now for Free!