This repository has been archived by the owner on Dec 11, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 972
Tearing off a tab causes the torn off site to display the wrong URL #8251
Labels
Milestone
Comments
FWIW @bsclifton & @bbondy I am unable to repro this in Windows 10 - 64bit Tearoffs working well, and displaying the URL for the tab that has been torn off. I've tried it with authenticated domains (Gmail), and Twitter (unauthenticated), and both display the proper URL in the tab that has been torn off. Profile info below for reference:
|
Reproduced on Windows and also found another interesting bug... will share a picture in a moment |
Wild 64bit or 32bit Windows? I've just tried reproducing again, and am seeing the appropriate URLs. |
@lukemulks 64-bit |
I can reproduce np, @lukemulks maybe you didn't pin first? No worries in any case I have a fix I'm about to push. |
bbondy
added a commit
that referenced
this issue
Apr 12, 2017
Auditors: @bsclifton Fix #8251 If a background tab event came in it would cause the active frame's input text to change. This could have caused some intermittent strangeness in urlbar previously as well The fix is to pass the frame path to update to updateNavBarInput so it doesn't use the active frame.
That was it. @bbondy @bsclifton I hadn't pinned, only tore off and
re-attached, and confused "pinned" with "re-attach".Sorry about that!
Awesome work on tearoff tabs!
On Apr 12, 2017 4:31 PM, "Brian R. Bondy" <notifications@github.com> wrote:
I can reproduce np, @lukemulks <https://github.com/lukemulks> maybe you
didn't pin first? No worries in any case I have a fix I'm about to push.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#8251 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AIkDKMfxPxILpY7l9XiJNljpayARUqIdks5rvV68gaJpZM4M7n20>
.
|
This was referenced Apr 13, 2017
This was referenced Apr 21, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Steps to reproduce
The text was updated successfully, but these errors were encountered: