tbb-dev

tbb-dev@lists.torproject.org

447 discussions

No more click-to-play barrier on YouTube: new feature, or regression?
by intrigeri 05 Aug '14

05 Aug '14

Hi, with TBB 3.6.3 (and possibly a few versions earlier), I see no click-to-play barrier on YouTube, while the manual test suite [1] still reads "Will have a NoScript click-to-play barrier, but should play after clicking it." So my question is: is the behavior I'm seeing a regression, or a new feature? If the former, then I'll file a Trac ticket about it. If the latter, then I will update the testing documentation. [1] https://trac.torproject.org/projects/tor/wiki/doc/build/BuildSignoff#TestPa… Cheers, -- intrigeri

2 2

Tor Browser Weekly IRC meetings moved to 18:00 UTC Mondays
by Mike Perry 01 Aug '14

01 Aug '14

Hello all, We've decided to relocate the Tor Browser team meeting to 18:00 UTC on Mondays (aka 20:00 CEST, 14:00 EDT, and 11:00 PDT). We've done this to try to shift the focus of our meetings towards planning for the coming week. I felt that with a meeting on Friday, we were too focused on what had been done, and that after the weekend, we'd already forgotten what we'd plan to do. That said, because it still will be useful to report what was actually done, and because a large amount of our workload is still devoted to reacting to issues that came up during the week, the overall meeting format will still be more or less in the form of the original post, just with more of an emphasis on what you plan to do rather than what you did: https://lists.torproject.org/pipermail/tbb-dev/2014-February/000000.htmla We'll also still be using the monthly trac keyword for tracking development plans. On Monday, we should plan to transfer the July tickets to August, and add or drop tickets as necessary: https://trac.torproject.org/projects/tor/query?keywords=~TorBrowserTeam2014… This change is effective immediately. Our next meeting is August 4th. We will not have the meeting this Friday (August 1st). -- Mike Perry

1 0

stopgap fix for ticket #9516 (Show log in Tor Browser)
by Mark Smith 01 Aug '14

01 Aug '14

Is it is too late to include a small but possibly important Tor Launcher improvement in TB 3.6.4? Please take a look at: https://trac.torproject.org/projects/tor/ticket/9516#comment:7 If Mike and others think the change is useful, it would be trivial to merge this fix into Tor Launcher's maint-0.2.5 branch (for TB 3.6.4). -- Mark Smith Pearl Crescent http://pearlcrescent.com/

2 1

Missing the meeting today
by Nicolas Vigier 25 Jul '14

25 Jul '14

Hello, I will be travelling this afternoon (unfortunately, to go to the funeral of my grandmother), so I won't be able to attend the meeting today. On the weekly update, the main thing I have been doing this week is the setup of the rebuild of all tor browser commits for xpcshell testing: https://lists.torproject.org/pipermail/tbb-dev/2014-July/000096.html Nicolas

1 0

Running xpcshell tests
by Nicolas Vigier 25 Jul '14

25 Jul '14

Hello, I am currently investigating how we can run the Mozilla xpcshell tests on our version of firefox, and the other unit tests. The xpcshell tests are included on the firefox source tree, and require a complete build tree, built without the '--disable-tests' option. So we cannot run those tests on the version that is shipped in the bundle. To run those tests, I can see different options: 1. Run the tests as part of the gitian build process and save the output in a file that can be analyzed later. The bundle build process is already very long, and we probably don't want to make it even longer. Running the xpcshell tests on my laptop (i5-2520M CPU @ 2.50GHz) took 2.5 hours. So this is probably not a good idea. 2. Save the build tree in a tarball at the end of the build, and make it available with the bundle files. We can then use it to run the tests as part of our test suite. The main problem with this is that the obj directory at the end of the build is taking 6GB. It's possible to reduce it to a 888MB tar.xz file, but it takes 50 minutes to create it on my laptop. 3. Build the browser separatly, in the VM that we use for running the tests. We enough test VMs to be able to do that. This also allow us to run those tests on any commit. The main problem with this is that we are not running the tests on the same binaries that are shipped in the bundle. So I'm thinking about doing 3. Does anybody have any other idea or comment about this ? Nicolas

3 6

weekly update from Pearl Crescent
by Mark Smith 17 Jul '14

17 Jul '14

I assume there will be a TBB dev meeting tomorrow... unfortunately, neither member of the Pearl Crescent team (Kathy Brade and myself) will be able to attend. Here is a brief update from us: * Related to #4234 (Firefox updater), we commented in child bugs #12622 and #12623, we looked at what it will take to rebase our patches onto the TBB 4.0a1 builder and browser code, and we researched symlink support for the Firefox updater (and filed #12647). https://trac.torproject.org/projects/tor/ticket/12622 "Automate update package distribution for TBB updater" https://trac.torproject.org/projects/tor/ticket/12623 "Deploy our TBB update archives on a secure machine" https://trac.torproject.org/projects/tor/ticket/12647 "updater needs to support use of symlinks" * For Tor Launcher and Torbutton, we fixed the Tor Launcher portion of #11193 (new logo in the config wizard that omits the word "Bundle"), we debugged #12264 and handed it to Isis for a fix, and we spent a bit of time fixing #11472. https://trac.torproject.org/projects/tor/ticket/11193 "Change Tor Browser Bundle to Tor Browser in package strings, download pages, and docs" https://trac.torproject.org/projects/tor/ticket/12624 "tbb-nightly-2014-07-13 chokes with 'Bad password or authentication cookie on controller.'" https://trac.torproject.org/projects/tor/ticket/11472 "Onion logo and text on about:tor page may overlap in non en-US TBBs" We also tried to help test the patches for #12391 and we triaged several miscellaneous bugs. https://trac.torproject.org/projects/tor/ticket/12391 "Building mingw-w64 is failing intermittently" * Next week we plan to focus on #12647 (symlink support for the updater) and rebasing of our updater patches. If we are overlooking anything that is of higher priority, let us know, -- Mark Smith Pearl Crescent http://pearlcrescent.com/

1 0

Feedback from help desk
by Matt Pagan 14 Jul '14

14 Jul '14

We've gotten some angry emails from users who have installed Tor for Windows (expert bundle) and been unable to uninstall it. I can confirm that although this package seems to keep up with the stable Tor releases pretty well, it definitely needs some love. For example, shortcuts (including a shortcut to an uninstaller) on Desktop and Start Menu are dead links. C:\Program Files(x86)\Tor appears never to have been created, although the shortcuts do get created. I can understand why getting a "Windows is searching for Uninstall.exe" message would be frustrating. It's not even clear for me how this package is created. Where is the source code?

1 1

Missing the meeting today
by Mike Perry 11 Jul '14

11 Jul '14

Hello everyone, Sorry for the short notice, but I won't be able to make the meeting today. I spent most of the week following up on dev meeting items and traveling, so not much to report from me anyway. I should be able to read the backlog, but i suspect a few others (gk, erinn?) are also traveling/will be absent, so it may be a short meeting. -- Mike Perry

1 0

Support report
by Matt Pagan 27 Jun '14

27 Jun '14

Hi browser devs, On account of being a Tor user, I have been banned from and unable to connect to OFTC since Tuesday. Hence, I'm sharing my help desk experiences asynchronously this week. A common request we see on the help desk is from users asking why they can't connect to some hidden service site. The reason is almost always that the site is down. However the message users see is Unable to connect Firefox can't establish a connection to the server at abcdefgh23456789.onion. This adds to the confusion users feel, as many don't understand why they see the word "Firefox" instead of "Tor Browser". In fact, any time during the user experience when users see the word "Firefox", genuine confusion seems to arise. A source of this confusion, I think, is that users thought they were using Tor Browser, not Firefox, and they begin to wonder if their current problem is somehow related to Mozilla Firefox, which may or may not also be installed on their computer. Actually I have seen users get quite angry from the confusion they feel at the general branding fail (not always from the "server might be down message" but from other Firefox references, for example, as seen in start up error messages). ------------- Matt Pagan matt(a)pagan.io

2 1

Make Tor Binary location configurable in Tor Launcher?
by Mike Perry 17 Jun '14

17 Jun '14

Hey Tails folks, hey Sukhbir, In our efforts to streamline and reorganize the Tor Browser directory structure for the Firefox updater, we have changed how Tor Launcher finds the Tor binary: https://trac.torproject.org/projects/tor/ticket/11641 https://gitweb.torproject.org/user/brade/tor-launcher.git/commitdiff/6599ac… We created a maint-0.2.5 Tor Launcher branch that preserves the old location and behavior for Tor Launcher 0.2.5.x releases in Tor Browser 3.6, while the master branch will house 0.2.6 and use this new directory structure for our upcoming 4.0-alpha series. While reviewing that patch, it occurred to me that it might be useful to make the path to the Tor binary configurable in a pref, rather than hardcoding the depth and pieces of the directory structure in the code and launching logic. However, it probably only makes sense to do this if it would also be useful to non-TBB consumers of Tor Launcher. Otherwise, we can keep using the hardcoded values just for us, if you guys already have an alternate way of launching Tor that you prefer. Let us know what you think! -- Mike Perry

3 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

tbb-dev