4 ms·

A Google representative has claimed on the domain hiding bug report that the change is shelved due to the feedback. Edit: Permalink to the relevant comment: ht

A Google representative has claimed on the domain hiding bug report that the change is shelved due to the feedback. Edit: Permalink to the relevant comment: https://bugs.chromium.org/p/chromium/issues/detail?id=883038#c60 https://bugs.chromium.org/p/chromium/issues/detail?id=883038...

danShumway 8y ago
Has it been shelved from Chrome 70? The last that I heard, it was temporarily removed in Chrome 69, and `www` would be reintroduced in 70. Unless things have changed again since then, `m` was the only change that was actually shelved.
- umanwizard 8y ago
  See my edit. They have confirmed it is not going live in 70.
  - danShumway 8y ago
    Nice! I'll be honest, I did not expect them to reverse course on that. That makes me a bit happier about this whole thing.
    - deleted 8y ago
      [deleted]
    - AsyncAwait 8y ago
      But it looks like it's going live post M70, is's not dead.
p1mrx 8y ago
Too bad there wasn't enough feedback about http:// http:// and https:// https:// hiding to make any difference. The biggest problem is that the two are hidden differently.
ken 8y ago
Yes, I think that's exactly what danShumway meant by "users have to do this every single release", i.e., give feedback about a big upcoming change that should never have been made in the first place. One week it's the domain hiding, another week it's cookie clearing. Who knows what Google is planning to change next time? It's not sustainable for us to go reactive every month. There's an awfully big disconnect if the makers of the world's most-used web browser are routinely trying to change it in ways that users force them to immediately revert. That's not what good stewards do.
- Lio 8y ago
  I feel this attitude of “just do it and see if enough people complain” is inherent in these big web companies. Just look at how they do product naming. How many times have we seen Google or Facebook launch projects with the same name as an existing project and just use their size to steamroll over refernce to the existing work? E.g. the Go programming language or Facebook’s Flow checker for starters.
- SquareWheel 8y ago
  >Who knows what Google is planning to change next time? It's not exactly a secret. Go download Canary and see what's in the pipeline.
  - AsyncAwait 8y ago
    You missed paren't point. It's not about if you can see the changes immediately in the next release, it's that you have to be constantly vigilant as to what they're going to do next, like looking over your shoulder. You can do that, but it's time consuming and exhausting. You're better off switching browsers.
    - SquareWheel 8y ago
      That's overly dramatic. Both Chrome and Firefox are excellent browsers, and are developed in the open for all to see. They are examples of open source done right.
walterbell 8y ago
The URL hiding change is NOT reversed or shelved, only delayed: > Thanks for the feedback so far. We plan to collect additional feedback, particularly about the enterprise use case, before launching the feature. We will not be launching the "www" elision in M70. Note: “before launching” the feature post-M70.
- umanwizard 8y ago
  Maybe it’s just a vocabulary quirk — to me, “shelved” implies “postponed indefinitely, but might come back someday”, not “cancelled forever”. So it is “shelved” according to how I understand that word. As you correctly point out, it’s not necessarily cancelled forever.
  - walterbell 8y ago
    Launching in M71 (i.e. delayed by a single release) would remain consistent with the Google statement. The statement applies to any delay within the range of "soon" and "not forever".
    - umanwizard 8y ago
      Yes, I agree with you. What was unclear about my comment?

danShumway 8y ago

Has it been shelved from Chrome 70? The last that I heard, it was temporarily removed in Chrome 69, and `www` would be reintroduced in 70. Unless things have changed again since then, `m` was the only change that was actually shelved.

umanwizard 8y ago
See my edit. They have confirmed it is not going live in 70.
- danShumway 8y ago
  Nice! I'll be honest, I did not expect them to reverse course on that. That makes me a bit happier about this whole thing.
  - deleted 8y ago
    [deleted]
  - AsyncAwait 8y ago
    But it looks like it's going live post M70, is's not dead.

p1mrx 8y ago

Too bad there wasn't enough feedback about http:// http:// and https:// https:// hiding to make any difference. The biggest problem is that the two are hidden differently.

ken 8y ago

Yes, I think that's exactly what danShumway meant by "users have to do this every single release", i.e., give feedback about a big upcoming change that should never have been made in the first place. One week it's the domain hiding, another week it's cookie clearing. Who knows what Google is planning to change next time? It's not sustainable for us to go reactive every month. There's an awfully big disconnect if the makers of the world's most-used web browser are routinely trying to change it in ways that users force them to immediately revert. That's not what good stewards do.

Lio 8y ago
I feel this attitude of “just do it and see if enough people complain” is inherent in these big web companies. Just look at how they do product naming. How many times have we seen Google or Facebook launch projects with the same name as an existing project and just use their size to steamroll over refernce to the existing work? E.g. the Go programming language or Facebook’s Flow checker for starters.
SquareWheel 8y ago
>Who knows what Google is planning to change next time? It's not exactly a secret. Go download Canary and see what's in the pipeline.
- AsyncAwait 8y ago
  You missed paren't point. It's not about if you can see the changes immediately in the next release, it's that you have to be constantly vigilant as to what they're going to do next, like looking over your shoulder. You can do that, but it's time consuming and exhausting. You're better off switching browsers.
  - SquareWheel 8y ago
    That's overly dramatic. Both Chrome and Firefox are excellent browsers, and are developed in the open for all to see. They are examples of open source done right.

walterbell 8y ago

The URL hiding change is NOT reversed or shelved, only delayed: > Thanks for the feedback so far. We plan to collect additional feedback, particularly about the enterprise use case, before launching the feature. We will not be launching the "www" elision in M70. Note: “before launching” the feature post-M70.

umanwizard 8y ago
Maybe it’s just a vocabulary quirk — to me, “shelved” implies “postponed indefinitely, but might come back someday”, not “cancelled forever”. So it is “shelved” according to how I understand that word. As you correctly point out, it’s not necessarily cancelled forever.
- walterbell 8y ago
  Launching in M71 (i.e. delayed by a single release) would remain consistent with the Google statement. The statement applies to any delay within the range of "soon" and "not forever".
  - umanwizard 8y ago
    Yes, I agree with you. What was unclear about my comment?