Announcement: using decltype for lazily loaded function

is available since MSVC 10. I decided to introduce it to Mozilla tree because Mozilla doesn't build on MSVC 9 or earlier. Please see bug 969918 for more details. Reagrds, Masatoshi Kimura ___ dev-platform mailing list dev-platform@lists.mozilla.org https

Re: Icon fonts in FxOS

(2014/06/17 4:34), Jet Villegas wrote: 1. Let people use the icon fonts anywhere. (ie. like MS WingDings can be used for this purpose) Actually WingDings can NOT be used at least on desktop Firefox because it does not have a unicode cmap. Does Firefox OS have an option to relax this

Re: Studying Lossy Image Compression Efficiency, July 2014

On 7/15/14 12:38 PM, stonecyp...@gmail.com wrote: Similarly there's a reason that people are still hacking video into JPEGs and using animated GIFs. People are using animated GIFs, but animated GIFs people are using may not be animated GIFs [1]. (2014/07/16 5:43), Chris Peterson wrote: Do

Re: Intent to implement and ship: Improved ruby parsing in HTML with new tag omission rules

On 2014/12/28 3:04, Michael[tm] Smith wrote: Further, I don't know of any typical case where if a base character is kana, why you'd ever want to display furigana/yomigana for it. Ruby is not used only for furigana/yomigana. I know one example from a very popular Japanese novel:

Intent to and unship: SSLv3

Summary: SSLv3 is an outdated and known broken security protocol. I'll remove the support from Gecko completely. Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1106470 Spec: https://tools.ietf.org/html/draft-ietf-tls-sslv3-diediedie-00 Platform coverage: All Target release: Gecko 39. Chrome

Re: Merge moved to Thursday 29th

I missed two commits for 44 branch. https://treeherder.mozilla.org/#/jobs?repo=fx-team=6b3c99e54177 Uplift requests will not help because they are string changes. On 2015/10/29 5:10, Sylvestre Ledru wrote: > Hello, > > Because we want to synchronize the release of 42 and 44 devedition (next >

Re: Intent to ship: RC4 disabled by default in Firefox 44

On 2015/09/02 1:56, Richard Barnes wrote: > * 42/ASAP: Disable whitelist in Nightly/Aurora; no change in Beta/Release > * 43: Disable unrestricted fallback in Beta/Release (thus allowing RC4 only > for whitelisted hosts) > * 44: Disable all RC4 prefs by default, in all releases The whitelist

Re: Intent to ship: referrerpolicy attribute

On 2016/01/04 16:54, Anne van Kesteren wrote: > There should be, per the specification discussion. E.g., > > function isSupported(token) { > var ele = document.createElement("a") > ele.referrerPolicy = token > return ele.referrerPolicy === token > } It didn't work because

Re: Intent to deprecate: MacOS 10.6-10.8 support

On 2016/03/11 3:03, Benjamin Smedberg wrote: > The motivation for this change is that we have continued failures that > are specific to these old operating systems and don't have the resources > on engineering teams to prioritize these bugs. Especially with the > deployment of e10s we're seeing

Re: #include sorting: case-sensitive or -insensitive?

On 2016/03/29 7:18, Jared Wein wrote: > We need to be careful with shuffling around #includes as there can be > ordering dependencies that are not obvious at a glance. Especially, #include "Foo.h" should be put first in Foo.cpp regardless of the alphabetical order to avoid introducing such

Re: Faster gecko builds with IceCC on Mac and Linux

Oh, my laptop has only 4 core and I won't buy a machine or a compiler farm account only to develope Gecko because my machine works perfectly for all my other puoposes. This is not the first time you blame my poor hardware. Mozilla (you are a Mozilla employee, aren't you?) does not want my

Re: The future of commit access policy for core Firefox

On 2017/03/10 6:53, Mike Connor wrote: >- Two-factor auth must be a requirement for all users approving or >pushing a change. I have no mobile devices. How can I use 2FA? Previously I was suggested to buy a new PC and SSD only to shorten the build time. Now do I have to buy a smartphone

Re: The future of commit access policy for core Firefox

On 2017/03/10 14:00, Mike Hommey wrote: > While we're talking about drag on productivity, there's already one that > comes from autoland already, which is that you can't easily land fixups > for stupid mistakes (like, a build failure on one platform, or other > lame things that happen when things

Please do not use GetNativePath and GetNativeTarget in XP code and Windows-specific code

On Windows, the native charset is not UTF-8. Using these functions will cause bugs such as [1] or [2]. Note that you can't simply replace all GetNative(Target|Path) to Get(Target|Path) + NS_ConvertUTF16toUTF8. It will make things *worse*. If you are using the path in logs or serialization formats

Re: Please do not use GetNativePath and GetNativeTarget in XP code and Windows-specific code

I intentionally ignored non-UTF-8 UNIX locales because our support for those locales is already half-broken and almost nobody cares about that. For example, OS.File assumes that the filesystem encoding is always UTF-8 on UNIX while nsIFile does not. This discrepancy caused a bug[1] that did not

Re: Dropping remains of support for non-UTF-8 file paths on Gtk platforms (was: Re: Please do not use GetNativePath and GetNativeTarget in XP code and Windows-specific code)

On 2017/12/04 20:19, Henri Sivonen wrote: > I suggest that instead of delaying with a round of telemetry, we make > all non-Windows platforms in nsNativeCharsetUtils.cpp use what's > currently the OSX/Android code path. +1 Some other data points: * If by any chance a profile path contains

Re: Phabricator/Lando update, November 2017

I went to the 2FA preference on BMO. For me, the only authentication option was TOTP that requires a smartphone. I do not have a smartphone like Mark. How can I continue to contribute after we are forced to use Phabricator? Mozilla no longer wants volunteer contributors? On 2017/11/30 3:05, Mark

Re: nsAutoConfig

On 2017/10/31 19:22, Marco Castelluccio wrote: > It is not covered by any automated test: > https://codecov.io/gh/marco-c/gecko-dev/src/9ca76dcb7a5c61d33750e9718c02b11ba35c1032/extensions/pref/autoconfig/src/nsAutoConfig.cpp > (this doesn't mean it isn't actually used ever, but it can be a clue).

Re: overly strict eslint rules

On 2017/12/25 6:31, Jonathan Kingston wrote: > It has worked for me for quite some time just running ./mach lint > filename.js after bootstrap. I got the following error when I tried it just now: --- $ mach lint

Re: error while building a release(official) version on window error: Gecko exception wrapping doesn't understand your your MSVC/SDK. Please file a bug describing this error and your build configurati

You cannot build Firefox 62 or earlier using Visual Studio 2017 Update 8 because of . On 2018/11/07 0:28, Amirhossein Ghafari wrote: > Hi, > > I'm trying to build the release version of the firefox on the windows host. > > The problem is I

Re: The tree has been reformatted now!

Unfortunately, the ‘format-source’ extension did not work for me. Please see . On 2018/11/30 23:46, Andi-Bogdan Postelnicu wrote: > Hello all > > Starting with revision 6f3709b3878117466168c40affa7bca0b60cf75b >

Re: Intent to Prototype: Have window.outerHeight/outerWidth lie and report the innerHeight/innerWidth

window.resizeTo() should also use innerHeight/innerWidth instead of outerHeight/outerWidth. Otherwise web pages can open a popup, call window.resizeTo(), and get innerHeight/innerWidth to circumvent the restriction. On 2019/09/08 13:57, Tom Ritter wrote: > Summary: > window.outerHeight/outerWidth

Re: Crash reports with Fission enabled are now indicated by DOMFissionEnabled = 1

On 2019/07/06 6:54, Andrew McCreight wrote: >> Here's an example of a crash report with DOMFissionEnabled: >> https://crash-stats.mozilla.org/report/index/dac0a91a-ad57-4446-9a82-505a80190705#tab-metadata I could not find `DOMFissionEnabled` in this crash report (although `DOMIPCEnabled` is