0
Welcome Guest! Login
0 items Join Now

HTML5 <nav> Tag

  • HTML5 <nav> Tag

    Posted 11 years 3 months ago
    • Hi

      Any particular reason why NAV tag is not used in current templates?

      Regards.
    • Hugo Avila
      Paginas Web
    • Who?'s Avatar
    • Who?
    • Preeminent Rocketeer
    • Posts: 25562
    • Thanks: 613
    • Joomla freelancer

    Re: HTML5 <nav> Tag

    Posted 11 years 3 months ago
    • Why exactly should we use it? We use RokNavMenu for main menu
    • Check my services at: Mihha-Vision
  • Re: HTML5 <nav> Tag

    Posted 11 years 3 months ago
    • Thanks Igor.
      Igor Mihaljko wrote:
      Why exactly should we use it?

      Exactly the same reason you are using <header>, <article>, <section>, etc. in HTML5 is all about semantics.

      Let me rephrase my original question: Why you are using some of the HTML5 tags but not usign <nav>?

      I know bootstrap wasn't using <nav> maybe due to IE8 compatibility, but they are using it right now. I dont know if they are sorting the issue with javascript like modernizr or similar.

      I am interested on <nav> because the benefits on accesibility, cleaner code, positioning, etc.

      Regars.
    • Hugo Avila
      Paginas Web
    • Who?'s Avatar
    • Who?
    • Preeminent Rocketeer
    • Posts: 25562
    • Thanks: 613
    • Joomla freelancer

    Re: HTML5 <nav> Tag

    Posted 11 years 3 months ago
    • As I said, we are using RokNavMenu for the main menu
    • Check my services at: Mihha-Vision
  • Re: HTML5 <nav> Tag

    Posted 11 years 3 months ago
    • Igor Mihaljko wrote:
      As I said, we are using RokNavMenu for the main menu

      Hi Igor, I am talking about the generated HTML, you could make RokNavMenu generate HTML5 tags or not. And RT choose to not use the <nav> tag.

      That is why I asked if RT have any particular reason to not use the tag.

      Kind Regards.
    • Hugo Avila
      Paginas Web
  • Re: HTML5 <nav> Tag

    Posted 11 years 3 months ago
    • RokNavMenu is been around for a while now and we have plans to rework our menu system entirely. The only reason we are not using <nav> at this state is because it would require some changes to RokNavMenu that might affect a lot of other templates. We feel like it's not worth adventuring into changing RokNavMenu right now, especially considering IE8 is not supported and it would require extra JS running that would quite certeinly slow down things more than IE8 already is.

      Yes <nav> is semantically more correct, better for search engines and what one should use nowadays, but to be entirely honest, it's not going to make any big impact on your site whether you use <nav> or not.
    • The following users have thanked you: Hugo Avila

    • / Djamil Legato / Lead Developer /

Time to create page: 0.093 seconds