Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

Typing a URL into the bar on a Pin Tab opens a new tab

  • 4 réponses
  • 2 ont ce problème
  • 10 vues
  • Dernière réponse par digama

more options

When I have a pinned tab open, typing a URL into the Awesome Bar and pressing enter causes a new tab to be opened, even if the URL is in the same domain as the original tab's location. Clicking links from the pin tab causes the tab to navigate normally (even out of the domain, if there are such links on the page). I run Firefox Nightly, and this appears to be a recent change in behavior, which I would like to revert via config change or something. Is anyone else aware of this change or why it was implemented?

When I have a pinned tab open, typing a URL into the Awesome Bar and pressing enter causes a new tab to be opened, even if the URL is in the same domain as the original tab's location. Clicking links from the pin tab causes the tab to navigate normally (even out of the domain, if there are such links on the page). I run Firefox Nightly, and this appears to be a recent change in behavior, which I would like to revert via config change or something. Is anyone else aware of this change or why it was implemented?

Toutes les réponses (4)

more options

Hi digama,

What versions of Nightly? take a look at [about:buildinfo] and we can file a bug with this, I do not know if this is intended behavior. Please also check if it happens in Safe Mode to be sure its not an add on Diagnose Firefox issues using Troubleshoot Mode

Thank you!

more options

I rather think this is a bug, since occasionally it will not open a new tab (I'm not sure about exactly what the criteria are for this, but it's rare, usually right after I switch to the tab the first time). Safe mode has no effect, and my about:buildconfig is (about:buildinfo does not exist):

about:buildconfig

Build Machine B-2008-IX-0104

Source Built from https://hg.mozilla.org/mozilla-central/rev/0894d2cdb16d

Build platform target i686-pc-mingw32

Build tools Compiler Version Compiler flags cl 1600 -TC -nologo -D_HAS_EXCEPTIONS=0 -W3 -Gy -wd4244 -wd4819 -we4553 cl 1600 -TP -nologo -D_HAS_EXCEPTIONS=0 -W3 -Gy -wd4251 -wd4244 -wd4345 -wd4351 -wd4482 -wd4800 -wd4819 -we4553 -GR- -DNDEBUG -DTRIMMED -Zi -UDEBUG -DNDEBUG -O1 -Oi -Oy-

Configure arguments --enable-crashreporter --enable-release --enable-update-channel=nightly --enable-update-packaging --enable-jemalloc --enable-require-all-d3dc-versions --with-google-api-keyfile=/c/builds/gapi.data --enable-warnings-as-errors --enable-signmar --enable-profiling --enable-js-diagnostics

more options

When you have a pinned tab and you type the URL (any URL for this case) in the pinned tab, it opens a new tab with the URL you typed, correct?

If so, that's the intended behavior for Nightly. It does the same thing to me. If you don't see the same thing then it's a bug and guigs2 will be able to help you with that report.

guigs2 take a break! ;)

Modifié le par Moses

more options

Moses,

If what you say is true, I have two comments:

This was not the behavior in previous versions of FF. I keep a pinned tab to a web 1.0 site with lots of intelligently named html files, so it's much easier for me to type the name of the page I want to see than to fumble with the gigantic index page. These are within-domain URL changes, so to me it seems perfectly reasonable to have pinned tabs not open a new tab in this case, and I thought that this had been intended behavior.

If this is "fixed" now, then I request that this be made a configuration option, because it conflicts with older behavior and there is (from my POV) a decent argument for reversing this decision. I use pin tabs because they don't scroll with the rest of the tabs and I want them to remain with their domains, but accepting all links and rejecting all URL adjustments seems not to actually achieve this, and instead makes an artificial distinction between two ways to get to the same place.

By the way, just because you see the same thing as I doesn't mean it's intended behavior, just that we are both running sufficiently up-to-date (or out-of-date) versions of FF. Unless you have another reason for asserting this?

Modifié le par digama