Meet the browser: Firefox Next


Recommended Posts

I will not discuss Health Report, Telemetry, Loop API, Developer Tools, UI Tour, Hello service, FxOS, Firefox for Android, Backend Sync, Release Engineering and many stupid stuff. UI Changes will be in Notable bugs.

After a while from mozilla-inbound:

 

- Compacting Generational GC landed in Nightly M37.

- Neowin Editor not working properly with Firefox Nightly adding spaces between paragraph or sometime adding space in start of line.

 

Cleanup, Removal & Dead Code

clean out unused Azure font options code - https://bugzilla.mozilla.org/show_bug.cgi?id=1109403

Remove some JSClass stub functions - https://bugzilla.mozilla.org/show_bug.cgi?id=1103152

Remove ValueToIntegerRange in jsstr.cpp - https://bugzilla.mozilla.org/show_bug.cgi?id=1107918

 

DOM

Avoid adding a shape guard on the proto in testCommonGetterSetter if the property is non-configurable - https://bugzilla.mozilla.org/show_bug.cgi?id=1100757

Make it impossible to use JS_Define* to redefine a non-configurable getter on a native object - https://bugzilla.mozilla.org/show_bug.cgi?id=1101123

Remove the expando hackery we have for window.window - https://bugzilla.mozilla.org/show_bug.cgi?id=1012798

 

Electrolysis

e10s - commands not updated properly - https://bugzilla.mozilla.org/show_bug.cgi?id=1060529

[e10s] Loading Spinner Doesn't Activate - https://bugzilla.mozilla.org/show_bug.cgi?id=1106936

[e10s] Wrong <select> dropdown widget on Windows and Linux - https://bugzilla.mozilla.org/show_bug.cgi?id=1053981

 

Layout

the < canvas > element returns incorrect min/pref inline-size in vertical writing modes - https://bugzilla.mozilla.org/show_bug.cgi?id=1108277

 

JS Engine
Odin: Tweak SIMD load/store error messages - https://bugzilla.mozilla.org/show_bug.cgi?id=1109096
SIMD: Support ?: on SIMD values - https://bugzilla.mozilla.org/show_bug.cgi?id=1108870
Rename SIMD.*.shiftLeft to SIMD.*.shiftLeftByScalar - https://bugzilla.mozilla.org/show_bug.cgi?id=1108807
Remove deprecated let block and add "use strict" in about:preferences - https://bugzilla.mozilla.org/show_bug.cgi?id=1108311
[leave open] Make the GC API strongly typed - https://bugzilla.mozilla.org/show_bug.cgi?id=1105069
[More so cleanup but still] Always build GGC features into SpiderMonkey - https://bugzilla.mozilla.org/show_bug.cgi?id=1107349
[More so cleanup but still] Always build IGC features into SpiderMonkey - https://bugzilla.mozilla.org/show_bug.cgi?id=1107288

Implement RegExp.prototype.flags - https://bugzilla.mozilla.org/show_bug.cgi?id=1108467

Make LIRGenerator visit() methods infallible - https://bugzilla.mozilla.org/show_bug.cgi?id=1107774

IonMonkey: Sink recoverable instructions - https://bugzilla.mozilla.org/show_bug.cgi?id=1093674

IonMonkey: support the x86/x64 VEX instruction encoding - https://bugzilla.mozilla.org/show_bug.cgi?id=1065339

 

Security
Limit wildcard DNS ID support to names of the form *.example.com (not foo*.example.com) - https://bugzilla.mozilla.org/show_bug.cgi?id=1107791
Remove support for absolute hostnames in presented DNS IDs and name constraints - https://bugzilla.mozilla.org/show_bug.cgi?id=1107790
Disable TLS_DHE_DSS_WITH_AES_128_CBC_SHA support - https://bugzilla.mozilla.org/show_bug.cgi?id=1107787
Remove preferences for cipher suites disabled - https://bugzilla.mozilla.org/show_bug.cgi?id=1037098

update the TLS version fallback limit pref loading code to only accept values in the range [0,3] - https://bugzilla.mozilla.org/show_bug.cgi?id=1093724

Disable insecure TLS version fallback - https://bugzilla.mozilla.org/show_bug.cgi?id=1084025

Service Worker
NS_ERROR_DOM_BAD_URI error using worker on url chrome://browser/content/browser.xul - https://bugzilla.mozilla.org/show_bug.cgi?id=1104623

 

WebGL

WebGL2 - Implement Buffer Objects - https://bugzilla.mozilla.org/show_bug.cgi?id=1048731

Enable D3D11 ANGLE by default - https://bugzilla.mozilla.org/show_bug.cgi?id=1079398

 

Notable Bugs

Fix pref for disabling onbeforeunload to still fire the relevant events - https://bugzilla.mozilla.org/show_bug.cgi?id=1107771

[leave open] The reason for showing a badge on the hamburger menu should be obvious when opening the menu - https://bugzilla.mozilla.org/show_bug.cgi?id=1105768

Make inContent preferences responsive - https://bugzilla.mozilla.org/show_bug.cgi?id=1026679

Remove temporary hidden pref for marketplace button on about:home - https://bugzilla.mozilla.org/show_bug.cgi?id=738646

Change implementation of BaseProxyHandler::set() to follow ES6 [[set]] specification - https://bugzilla.mozilla.org/show_bug.cgi?id=1083211

[MemShrink] (cumulative-heap-profiling) DMD: support cumulative heap profiling - https://bugzilla.mozilla.org/show_bug.cgi?id=1094552

ContentSearch should load the search URL in the browser/tab sending the search message, not the current/selected browser in the top-level chrome window - https://bugzilla.mozilla.org/show_bug.cgi?id=1096534

APZ needs mouse wheel transactions - https://bugzilla.mozilla.org/show_bug.cgi?id=1013432

csp.newbackend blocks sources containing ";" - https://bugzilla.mozilla.org/show_bug.cgi?id=1094067

[leave open] Search dropdown footer and open search items have an inconsistent styling with the australis panels - https://bugzilla.mozilla.org/show_bug.cgi?id=1106569

[Linux] Theme issues with GTK 3.14 - https://bugzilla.mozilla.org/show_bug.cgi?id=1073117

 

RANDOM

Remove the WindowsJumpLists.jsm depedency on hasHistoryEntries - https://bugzilla.mozilla.org/show_bug.cgi?id=1101478

Upgrade in-tree SQLite to 3.8.7.4 - https://bugzilla.mozilla.org/show_bug.cgi?id=1108328

4.29% Linux|win|osx Dromaeo DOM regression on Inbound (v.36) Nov 25 - https://bugzilla.mozilla.org/show_bug.cgi?id=1106784

MFBT: Add a SegmentedVector type - https://bugzilla.mozilla.org/show_bug.cgi?id=1102525

[Oldie] xpcwrappedjsclass.cpp rev 1.73 regressed "return" of NS_COMFALSE (Components.returnCode) - https://bugzilla.mozilla.org/show_bug.cgi?id=287107

Link to comment
Share on other sites

Just noticed this:

 

Screenshoton2014-12-15at14.40.04.png

 

It looks as though Mozilla are pulling a Wikipedia by asking for donations right on the default start page.

Link to comment
Share on other sites

I really don't want to open a new thread for this, so I'll post here: is this a Neowin problem or a Firefox problem? I'm pretty sure the icon shouldn't look like this. Didn't try on other browsers, only Firefox.

 

y43t.png

It's the Neowin bookmark on the Bookmarks bar.

Link to comment
Share on other sites

It's a problem on your end. I don't keep the bookmarks titled in my toolbar (looks cleaner without them), but just added a name to the bookmark and it's displayed fine:

QYel5OM.jpg

 

Using the latest stable release of Firefox and no extensions that modify the the default theme somehow.

 

edit: Wait, you mean the actual favicon? If so, no problem there.

Link to comment
Share on other sites

It's a problem on your end. I don't keep the bookmarks titled in my toolbar (looks cleaner without them), but just added a name to the bookmark and it's displayed fine:

QYel5OM.jpg

 

Using the latest stable release of Firefox and no extensions that modify the the default theme somehow.

 

edit: Wait, you mean the actual favicon? If so, no problem there.

Well, your picture looks exactly the same as mine. :/

Yes, I mean the icon. Look at the edge of the icon, you'll know what I mean.

Link to comment
Share on other sites

 
 

 

Just noticed this:

 

Screenshoton2014-12-15at14.40.04.png

 

It looks as though Mozilla are pulling a Wikipedia by asking for donations right on the default start page.

 

 

so yahoo not pay them enough :p that was a ____ move by mozilla to have them and then beg for money...

Link to comment
Share on other sites

Well, your picture looks exactly the same as mine. :/

Yes, I mean the icon. Look at the edge of the icon, you'll know what I mean.

Yes, the favicon looks bad (meaning it's all jagged around the edges and not smooth) when logged in with an account on the main site - it only happens when you're logged in with a account, if you log out and F5 the main page it'll look fine. Report it as a site issue.

Link to comment
Share on other sites

Yes, the favicon looks bad (meaning it's all jagged around the edges and not smooth) when logged in with an account on the main site - it only happens when you're logged in with a account, if you log out and F5 the main page it'll look fine. Report it as a site issue.

Thank you, I just wanted to be sure that I wasn't the only one with this issue. :)

Link to comment
Share on other sites

Since yesterday's build I have been unable to right click and open in new tab or window. Is anyone else having this problem? Broken in new profile as well.

Link to comment
Share on other sites

Link to comment
Share on other sites

While Fabrice Bellard's work on the BPG Image Format has been getting a lot of attention in recent weeks for being an image format trying to replace JPEGs with offering higher compression ratio and other features over JPEGs, its design around the encoding of HEVC/H.265 makes its blocked by patents. For at least the interim, Mozilla is committed to making JPEGs better for the web.

Mozilla developers have been working hard on their own JPEG encoding library dubbed "MozJPEG" and it's been progressing very well with offering improved better compression ratios while remaining standards compliant.

MozJPEG 3.0 is around the corner and it improves JPEG encoding even more. Kornel Lesi?ski has written about some of the work that's happened for MozJPEG 3.0 including cleaner black-on-white text and lines, a common future-proof API to share with libjpeg-turbo, etc.

 

MozJPEG

Link to comment
Share on other sites

BPG would be a nice replacement for JPEG (Daala being years off), but the patent issue makes it a mess at the moment (A browser could implement it on Windows 10, but that's it). And I do find it rather funny how we're replacing a still picture format with a motion picture format (The main benefits of HEVC and the like is how good they are at encoding moving pictures, still frames are only used for keyframes, and the quality difference isn't huge, it's more the lack of blocky artifacts)

Honestly the main improvements is higher colour depth (and channel) support, that's a weak area for JPEG, and Google's replacement isn't even as good as JPEG here. Although BPG is still really limited to RGB(A)/YUV(A)/CMYK(A), while JPEG-XR supported arbitrary colour formats (So you could encode things like infra-red data alongside colour data).

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now