Recommended Posts

Is anyone else having issues with the tab titles?

Example:

post-2-1291730397589.png

The tab title doesn't change with the page title (this happens on most sites). Sometimes reused tabs keep the old domain title while I'm somewhere else too? :p

The in-content UI change is a start, but it looks pretty bland compared to the mockups. I'm hoping we can start getting more eye candy after beta 8 wraps up.

Is anyone else having issues with the tab titles?

Example:

post-2-1291730397589.png

The tab title doesn't change with the page title (this happens on most sites). Sometimes reused tabs keep the old domain title while I'm somewhere else too? :p

I haven't had this problem, but I saw it in bugzilla yesterday - Bug 616916. It's currently unconfirmed, so maybe posting your screenshot there will get it more notice?

Also, don't forget to try in Safe Mode or with a new profile. ;)

Is anyone else having issues with the tab titles?

Example:

post-2-1291730397589.png

The tab title doesn't change with the page title (this happens on most sites). Sometimes reused tabs keep the old domain title while I'm somewhere else too? :p

have you tried disabling your stylish scripts?

maybe one of them is conflicting

So a bunch of the Google guys working on Chrome have found a pretty fatal flaw* in the current WebSocket protocol, and it's going to require some breaking changes to the foundation to get it into a usable state.

And because of the time/schedule, those changes won't make Firefox 4, and as such WebSockets support will be disabled for the final release. I think this is a good example of not rushing into supporting a spec too early, multiple versions of Chrome have shipped with WebSockets support enabled, some incompatible with other versions of Chrome, and all with this flaw.

* With a correctly formatted response, you can trick buggy proxies into thinking any random bit of data comes from another site, e.g. you could overwrite Google's Analytics code for every user on the proxy.

A new performance tracker landed in the latest nightly, it records when the app was started and how long it takes for it to actually launch.

190075043t.png

Obviously it'll become more useful over time, I'm surprised it only took 4 seconds to start on my Mac (considering it has 2GB of RAM and I have like 30 tabs open in multiple TabCandy groups)

Edit: And it just got backed out due to crashes :laugh:

AWFY's with kraken and v8 bench (updated till Dec 8) : http://www.arewefastyet.com/awfy2.php

Strange; this makes it seem like V8 doesn't have Crankshaft enabled? That should bring it close to Mozilla's TM+JM scores on Kraken. There's a huge difference.

It's strange because V8 already have this feature supported in the latest builds that AWFY should cover in that graph.

V8 should also receive a bump on v8bench, and be the current winner on Sunspider once this optimizing compiler is enabled.

Strange; this makes it seem like V8 doesn't have Crankshaft enabled? That should bring it close to Mozilla's TM+JM scores on Kraken. There's a huge difference.

It's strange because V8 already have this feature supported in the latest builds that AWFY should cover in that graph.

V8 should also receive a bump on v8bench, and be the current winner on Sunspider once this optimizing compiler is enabled.

It's barely been out a day! Plus, it's only in specific developer builds, give it a little time to mature (and appear in AWFY)

(Don't get me wrong though, looks like a great development)

Spot the changed default as of today's nightly:

post-1302-12919053103213.png

(OS X default theme with default toolbar settings)

I was removing the home button entirely.

(Not saying that's what should have been done. I read over the bug page too, so I understand why, and agree with just moving it.)

EDIT: Are they really going to connect the home and bookmark buttons together?

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • "...a low price of just $340..." I don't think it means what you think it means.
    • This Corsair Vengeance DDR5-6000 32GB RAM with RGB is a great deal for limited time by Sayan Sen Memory prices have been through the roof for a while, though it seems like things might finally be getting better. If you are in the market for one, then grab this Corsair Vengeance DDR5 32GB (2x16GB) DDR5 6000 CL36 kit with RGB for a low price of just $340 (purchase link under the specs table down below). The kit is compatible with both AMD and Intel systems as it supports both EXPO and XMP overclocking profiles, respectively. 6000 MT/s is often the sweet spot for many systems as it provides ample data transfer speed while still being on Gear 1 mode. This Vengeance variant has RGB so if you love bright setups with such lighting, this is a win-win for you. The technical specifications of the Corsair Vengeance memory kit are given in the table below: Specification Value Memory Type DDR5 Memory Size (Total) 32GB Kit Configuration 2 × 16GB Form Factor UDIMM (Desktop) Pin Count 288-pin Speed (Data Rate) 6000 MT/s Speed Rating PC5-48000 Tested CAS Latency 38-44-44-96 Voltage (Tested) 1.35V Performance Profile AMD EXPO & Intel XMP Heat Spreader Aluminum heatspreader Cooling Type Passive (Heatsink) Lighting Ten Zone RGB Software Support Corsair iCUE Get it at the link below: CORSAIR Vengeance RGB DDR5 32GB (2 x 16GB) 6000 CL38 – Gray (CMH32GX5M1E6000Z38): $339.99 (Sold and Shipped by Woot US, Fulfilled by Amazon US) This Woot deal is US-specific and not available in other regions unless specified. This is a first-party seller link (at the time of article publishing); ensure that you also purchase from a first-party seller link only. If you don't like it or want to look at more options, check out the previous deals that we have covered, OR you can also visit Amazon US deals page. Get Prime (SNAP), Prime Video, Audible Plus or Kindle / Music Unlimited. Free for 30 days. As an Amazon Associate, we earn from qualifying purchases.
    • The very fact that a TPM (v2.0 specifically which is part of the issue I suspect) is now a baseline for any supported Windows installation will naturally mean other vendors will start to leverage it as they know it'll be there. It's called progress, and it's always been the way. A TPM isn't a windows thing, it's just a module designed to securely store keys. Secure boot isn't a Windows thing (although MS are the TCA as I recall hence the upheaval this year as the 2011 certs expire), it's just a way to verify a bootloader is signed. Windows simply leverages them.
    • It's a local account with the ability to reset a password at a very base level. I really don't get the issue that gets whipped up around it But you do you
  • Recent Achievements

    • Proficient
      Eric Biran went up a rank
      Proficient
    • Dedicated
      Conjor earned a badge
      Dedicated
    • Week One Done
      Windows Guy earned a badge
      Week One Done
    • Dedicated
      Mark Spruce earned a badge
      Dedicated
    • Collaborator
      conkir earned a badge
      Collaborator
  • Popular Contributors

    1. 1
      +primortal
      479
    2. 2
      PsYcHoKiLLa
      244
    3. 3
      Steven P.
      72
    4. 4
      +Edouard
      66
    5. 5
      Skyfrog
      65
  • Tell a friend

    Love Neowin? Tell a friend!