Google Chrome Has New gTLD Bug…Or Is It A Bug?

As you all know I have been very vocal about my excitement around new gTLDs. As you also know I don’t think new gTLDs represent investment opportunities for Domainers, I do think they will be great for startups and small businesses. So I was excited to read this morning that Frank Schilling’s Uniregistry had brought .tatoo live. So I typed nic.tatto into the URL bar of my browser to get to the main page for the gTLD.

Here’s what I got:

nic-tattoo

 

Rather than taking me to nic.tattoo, just like I would get to tattoo.com if I typed it in the URL bar, I ended-up with a search result for nic.tattoo of which as you can see, there’s no listing for nic.tattoo. When I looked the top of my browser window a saw a small grey bar that said, “Did you mean http://nic.tattoo?”

I clicked the “Yes” button and then ended-up at nic.tattoo. Ah Houston, we have a problem. Google should definitely change this otherwise every new gTLD is going to leave users with the search results for the URL they were looking for rather than sending them to the site. The grey stripe that drops down will definitely be missed by users and since the search results don’t have the website for nic.tattoo in them, that makes things even more confusing.

Okay, now I don’t want all the new gTLD naysayers to jump on here and say “I told you so!” With anything new there will be a period of adjustment, I just hope Google makes that adjustment soon because as far as I’m concerned, Chrome as a new gTLD bug…or is it a bug?

{ 10 comments… add one }

  • Anonymous November 15, 2013, 9:32 am

    What, or who, is ‘nic’ in this context?

    Reply
  • HowieCrosby November 15, 2013, 9:58 am

    Hi Morgan,

    Re. your first sentence…
    I’m slightly confused with the matter of the poor investment opportunities for Domainers in the gTLDs and the great opportunities for startups and small businesses in the gTLDs?

    If a wise domain investor cherry picked a portfolio of new gTLDs and then went on to sell them on to start ups, much the same as your good self does with the .com, this would make it an opportunity for the domain investor would it not?

    I am concerning the conversation with the catchy (one word.gTLD)

    Furthermore, I see a new generation or evolving generation using between the dots.

    Moreover, pro .com domainer Rick Schwartz said something along the lines “why not own both.” during the recent Vegas “.com/New gTLD” showdown.

    Best,

    Howie.

    Reply
  • eCommerce November 15, 2013, 2:35 pm

    Not a bug. Just another reason why the gTLD’s are for fools and will surely fail flat on their silly-assed faces.

    Reply
  • Homero A. Gonzalez November 15, 2013, 5:49 pm

    Morgan, this is a bug. I reported it to Google. Have you tried in other browsers? IE safari opera firefox? Cheers!

    Reply
  • Math Two November 15, 2013, 8:03 pm

    C’mon Morgan — what’s the difference — it’s not like an end user is actually ever going to go there!

    Reply
    • Morgan November 15, 2013, 11:02 pm

      @Math Two – do you honestly think people are never going to figure-out how to type anything except for a .COM?

      Reply
  • Alan Dodd, namedream.com November 17, 2013, 8:51 am

    This looks like a one off detail, that when it’s fixed, all the new tlds will be fixed.

    Or at least you would hope so! It’s curious, though, as to why Chrome was not ready for this change.

    I must say, this new Gtld thing is great. Believe you me – the more, themerrior.com!

    Reply
  • Homero A. Gonzalez November 18, 2013, 8:12 pm

    Morgan, its is fixed. Was that fast enough? I have checked it just on chrome in my nexus 7 tablet. Check in other platforms/ os and let us know.

    Reply
  • George S February 10, 2014, 8:25 am

    Safari still exhibits this problem. Chrome appears to be fixed.

    Reply
  • Magnus May 15, 2014, 5:10 am

    Nope! Chrome’s still got the problem (smartphone).

    Reply

Leave a Comment