dev-platform  

Messages by Thread

• • Re: XPCOM Tidying Proposal Kyle Machulis
  • Re: XPCOM Tidying Proposal Boris Zbarsky
  • Re: XPCOM Tidying Proposal Bobby Holley
  • Re: XPCOM Tidying Proposal Kyle Machulis
  • Re: XPCOM Tidying Proposal Bobby Holley
  • Re: XPCOM Tidying Proposal Kyle Machulis
• Re: Coming in Firefox 65: Dedicated Profiles Per Install and Profile Downgrade Protection Dave Townsend via dev-platform
• Intent to implement: report-to header as part of Reporting API Andrea Marchesini
  • Re: Intent to implement: report-to header as part of Reporting API David Burns
  • Re: Intent to implement: report-to header as part of Reporting API Andrea Marchesini
  • Re: Intent to implement: report-to header as part of Reporting API Ehsan Akhgari
  • Re: Intent to implement: report-to header as part of Reporting API Andrea Marchesini
• Rust code coverage Marco Castelluccio
  • Re: Rust code coverage Bobby Holley
  • Re: Rust code coverage Henri Sivonen
  • Re: Rust code coverage Marco Castelluccio
• PSA: nsIDocument is now mozilla::dom::Document. Emilio Cobos Álvarez
  • Re: PSA: nsIDocument is now mozilla::dom::Document. Bobby Holley
  • Re: PSA: nsIDocument is now mozilla::dom::Document. Tim Guan-tin Chien
  • Re: PSA: nsIDocument is now mozilla::dom::Document. Jeff Muizelaar
• Proposal to adjust testing to run on PGO builds only and not test on OPT builds jmaher
  • Re: Proposal to adjust testing to run on PGO builds only and not test on OPT builds Tom Ritter
  • Re: Proposal to adjust testing to run on PGO builds only and not test on OPT builds James Graham
  • Re: Proposal to adjust testing to run on PGO builds only and not test on OPT builds Brian Grinstead
  • Re: Proposal to adjust testing to run on PGO builds only and not test on OPT builds Nicholas Alexander
  • Re: Proposal to adjust testing to run on PGO builds only and not test on OPT builds Henrik Skupin
  • Re: Proposal to adjust testing to run on PGO builds only and not test on OPT builds Andrew Halberstadt
  • Re: Proposal to adjust testing to run on PGO builds only and not test on OPT builds Justin Wood
  • Re: Proposal to adjust testing to run on PGO builds only and not test on OPT builds Steve Fink
  • Re: Proposal to adjust testing to run on PGO builds only and not test on OPT builds Justin Wood
  • Re: Proposal to adjust testing to run on PGO builds only and not test on OPT builds Jan de Mooij
  • Re: Proposal to adjust testing to run on PGO builds only and not test on OPT builds Aki Sasaki
  • Re: Proposal to adjust testing to run on PGO builds only and not test on OPT builds Brian Grinstead
  • Re: Proposal to adjust testing to run on PGO builds only and not test on OPT builds Jonathan Kew
  • Re: Proposal to adjust testing to run on PGO builds only and not test on OPT builds Steve Fink
  • Re: Proposal to adjust testing to run on PGO builds only and not test on OPT builds James Graham
  • Re: Proposal to adjust testing to run on PGO builds only and not test on OPT builds Chris AtLee
  • Re: Proposal to adjust testing to run on PGO builds only and not test on OPT builds Nicholas Alexander
  • Re: Proposal to adjust testing to run on PGO builds only and not test on OPT builds Nathan Froyd
  • Re: Proposal to adjust testing to run on PGO builds only and not test on OPT builds jmaher
  • Re: Proposal to adjust testing to run on PGO builds only and not test on OPT builds Randell Jesup
  • Re: Proposal to adjust testing to run on PGO builds only and not test on OPT builds Chris M.
  • Re: Proposal to adjust testing to run on PGO builds only and not test on OPT builds jmaher
  • Re: Proposal to adjust testing to run on PGO builds only and not test on OPT builds James Graham
  • Re: Proposal to adjust testing to run on PGO builds only and not test on OPT builds Jan de Mooij
  • Re: Proposal to adjust testing to run on PGO builds only and not test on OPT builds Joel Maher
  • Re: Proposal to adjust testing to run on PGO builds only and not test on OPT builds Jan de Mooij
  • Re: Proposal to adjust testing to run on PGO builds only and not test on OPT builds James Graham
  • Re: Proposal to adjust testing to run on PGO builds only and not test on OPT builds Eric Rahm
• Intent to restrict to secure contexts: navigator.geolocation llisamarielindsay
  • Re: Intent to restrict to secure contexts: navigator.geolocation gordonjoe636
  • Re: Intent to restrict to secure contexts: navigator.geolocation Bagher Sadati
• Post-Holiday reviews and needinfo responses Ryan VanderMeulen
• Skipping changesets when viewing blame Felipe G
  • Re: Skipping changesets when viewing blame Dave Townsend
• How to use Phabricator the correct way soeren.hentzschel--- via dev-platform
  • Re: How to use Phabricator the correct way Alex Gaynor
• Proposed W3C Charter: SVG Working Group L. David Baron
  • Re: Proposed W3C Charter: SVG Working Group Henri Sivonen
  • Re: Proposed W3C Charter: SVG Working Group Cameron McCormack
  • Re: Proposed W3C Charter: SVG Working Group Henri Sivonen
  • Re: Proposed W3C Charter: SVG Working Group Cameron McCormack
  • Re: Proposed W3C Charter: SVG Working Group L. David Baron
  • Re: Proposed W3C Charter: SVG Working Group Tantek Çelik
  • Re: Proposed W3C Charter: SVG Working Group L. David Baron
• Intent to implement and ship: Overflow media queries Emilio Cobos Álvarez
  • Re: Intent to implement and ship: Overflow media queries James Graham
  • Re: Intent to implement and ship: Overflow media queries Emilio Cobos Álvarez
  • Re: Intent to implement and ship: Overflow media queries fantasai
• Re: Better incremental builds - Tup backend available on Linux kmoir
• PSA: Android Hardware testing on Try only available via mach try fuzzy Bob Clary
• PSA - If --disable-e10s is crashing for you on Windows... Tom Ritter
• JS components and modules, subscripts loaded via the subscript loader, mochitest-browser tests, and SJS scripts are now exclusively UTF-8 Jeff Walden
• arm64 windows nightlies now available Nathan Froyd
  • Re: arm64 windows nightlies now available Kim Moir
• Pointer to the stack limit Henri Sivonen
  • Re: Pointer to the stack limit David Major
  • Re: Pointer to the stack limit Henri Sivonen
  • Re: Pointer to the stack limit Kris Maglione
• Intent to ship: Storage Access API Ehsan Akhgari
• PSA: Compartments will soon contain multiple global objects Jan de Mooij
  • Re: PSA: Compartments will soon contain multiple global objects Ehsan Akhgari
• Landing in 66: force opt-in to run extensions in private browsing Shane Caraveo
• Intent to implement: TextEncoder.encodeInto() - UTF-8 encode into caller-provided buffer Henri Sivonen
  • Intent to ship: TextEncoder.encodeInto() - UTF-8 encode into caller-provided buffer Henri Sivonen
  • Re: Intent to ship: TextEncoder.encodeInto() - UTF-8 encode into caller-provided buffer Boris Zbarsky
  • Re: Intent to ship: TextEncoder.encodeInto() - UTF-8 encode into caller-provided buffer Henri Sivonen
• PSA: Landing Rust code that warns is no longer ok Emilio Cobos Álvarez
  • Re: PSA: Landing Rust code that warns is no longer ok Xidorn Quan
  • Re: PSA: Landing Rust code that warns is no longer ok Emilio Cobos Álvarez
  • Re: PSA: Landing Rust code that warns is no longer ok Kris Maglione
• Re: web-platform-tests that fail only in Firefox (from wpt.fyi data) Philip Jägenstedt
  • Re: web-platform-tests that fail only in Firefox (from wpt.fyi data) Philip Jägenstedt
  • Re: web-platform-tests that fail only in Firefox (from wpt.fyi data) David Burns
  • Re: web-platform-tests that fail only in Firefox (from wpt.fyi data) Philip Jägenstedt
• Intent to ship: InputEvent.inputType (with Input Events Level 1) Masayuki Nakano
• Disabling IPC protocol with build flags? docfaraday
  • Re: Disabling IPC protocol with build flags? Tom Ritter
  • Re: Disabling IPC protocol with build flags? Nathan Froyd
• Intent to unship: x-moz-errormessage attribute Andrea Marchesini
• Intent to implement and ship: forced case-sensitive attribute selector matching Boris Zbarsky
  • Re: Intent to implement and ship: forced case-sensitive attribute selector matching fantasai
• Re: Performance profiling improvements #3 Markus Stange
• Slides from Orlando platform memory tools meeting Jim Blandy
• Intent to implement and ship: UTF-8 autodetection for HTML and plain text loaded from file: URLs Henri Sivonen
  • Re: Intent to implement and ship: UTF-8 autodetection for HTML and plain text loaded from file: URLs Martin Thomson
  • Re: Intent to implement and ship: UTF-8 autodetection for HTML and plain text loaded from file: URLs Henri Sivonen
  • Re: Intent to implement and ship: UTF-8 autodetection for HTML and plain text loaded from file: URLs Henri Sivonen
  • Re: Intent to implement and ship: UTF-8 autodetection for HTML and plain text loaded from file: URLs Martin Thomson
• Next Year in web-platform-tests - 2018/19 Edition James Graham
  • Re: Next Year in web-platform-tests - 2018/19 Edition Nils Ohlmeier
• This year in web-platform-tests - 2018 edition James Graham
  • Re: This year in web-platform-tests - 2018 edition Bobby Holley
• Intent to Implement and Ship: break-before, break-after, break-inside CSS properties Emilio Cobos Álvarez
  • Re: Intent to Implement and Ship: break-before, break-after, break-inside CSS properties Eric Shepherd (Sheppy)
  • Re: Intent to Implement and Ship: break-before, break-after, break-inside CSS properties Emilio Cobos Álvarez
• Checking if an nsIURI came from a resource: URL Henri Sivonen
  • Re: Checking if an nsIURI came from a resource: URL Daniel Veditz
  • Re: Checking if an nsIURI came from a resource: URL Henri Sivonen
  • Re: Checking if an nsIURI came from a resource: URL Dave Townsend
  • Re: Checking if an nsIURI came from a resource: URL Henri Sivonen
• Dropping support for compiling with MSVC in the near future Ted Mielczarek
  • Re: Dropping support for compiling with MSVC in the near future Kris Maglione
  • Re: Dropping support for compiling with MSVC in the near future Jonathan Kew
  • Re: Dropping support for compiling with MSVC in the near future Kris Maglione
  • Re: Dropping support for compiling with MSVC in the near future Gabriele Svelto
  • Re: Dropping support for compiling with MSVC in the near future Kris Maglione
  • Re: Dropping support for compiling with MSVC in the near future Ted Mielczarek
  • Re: Dropping support for compiling with MSVC in the near future Gijs Kruitbosch
  • Re: Dropping support for compiling with MSVC in the near future Nathan Froyd
  • Re: Dropping support for compiling with MSVC in the near future Honza Bambas
  • Re: Dropping support for compiling with MSVC in the near future Simon Sapin
  • Re: Dropping support for compiling with MSVC in the near future Ted Mielczarek
  • Re: Dropping support for compiling with MSVC in the near future Ted Mielczarek
  • Re: Dropping support for compiling with MSVC in the near future Jim Mathies
  • Re: Dropping support for compiling with MSVC in the near future Kartikaya Gupta
  • Re: Dropping support for compiling with MSVC in the near future Ted Mielczarek
  • Re: Dropping support for compiling with MSVC in the near future Kartikaya Gupta
  • Re: Dropping support for compiling with MSVC in the near future Mike Hommey
• Re: Intent to ship: Enable navigator.clipboard.* APIs by default charliewang0104
• HG problem: abort: decoding near '9: error: ‘sse2::l': 'ascii' codec can't decode byte 0xe2 in position 213: ordinal not in range(128) ISHIKAWA,chiaki
  • Re: HG problem: abort: decoding near '9: error: ‘sse2::l': 'ascii' codec can't decode byte 0xe2 in position 213: ordinal not in range(128) Dave Townsend
  • Re: HG problem: abort: decoding near '9: error: ‘sse2::l': 'ascii' codec can't decode byte 0xe2 in position 213: ordinal not in range(128) ISHIKAWA,chiaki
• What is future of editor mode-lines after the switch to clang-format? tcampbell
  • Re: What is future of editor mode-lines after the switch to clang-format? Ehsan Akhgari
  • Re: What is future of editor mode-lines after the switch to clang-format? Nathan Froyd
  • Re: What is future of editor mode-lines after the switch to clang-format? Tom Tromey
  • Re: What is future of editor mode-lines after the switch to clang-format? Ehsan Akhgari
  • Re: What is future of editor mode-lines after the switch to clang-format? Andrew McCreight
  • Re: What is future of editor mode-lines after the switch to clang-format? Gregory Szorc
  • Re: What is future of editor mode-lines after the switch to clang-format? Ehsan Akhgari
  • Re: What is future of editor mode-lines after the switch to clang-format? Ehsan Akhgari
  • Re: What is future of editor mode-lines after the switch to clang-format? Gregory Szorc
  • Re: What is future of editor mode-lines after the switch to clang-format? Mike Hommey
• Re: Upcoming C++ standards meeting in San Diego, California Botond Ballo
• The tree has been reformatted now! Andi-Bogdan Postelnicu
  • Re: The tree has been reformatted now! Andi-Bogdan Postelnicu
  • Re: The tree has been reformatted now! Emilio Cobos Álvarez
  • Re: The tree has been reformatted now! Masatoshi Kimura
• Intent to ship: window.event Masayuki Nakano
  • Re: Intent to ship: window.event Masayuki Nakano
• Intent to ship: set keyCode or charCode of "keypress" event to the other's non-zero value Masayuki Nakano
  • Re: Intent to ship: set keyCode or charCode of "keypress" event to the other's non-zero value James Graham
  • Re: Intent to ship: set keyCode or charCode of "keypress" event to the other's non-zero value Masayuki Nakano
  • Re: Intent to ship: set keyCode or charCode of "keypress" event to the other's non-zero value James Graham
  • Re: Intent to ship: set keyCode or charCode of "keypress" event to the other's non-zero value Masayuki Nakano
• Intent to ship: stop dispatching "keypress" events when pressed key (key combination) does not introduce text input Masayuki Nakano
  • Re: Intent to ship: stop dispatching "keypress" events when pressed key (key combination) does not introduce text input Eli Grey via dev-platform
  • Re: Intent to ship: stop dispatching "keypress" events when pressed key (key combination) does not introduce text input Eli Grey via dev-platform
  • Re: Intent to ship: stop dispatching "keypress" events when pressed key (key combination) does not introduce text input Masayuki Nakano
• Intent to ship: dispatching "keydown" and "keyup" events during IME composition Masayuki Nakano
• Re: Intent to unship: -moz-prefixed CSS gradient functions dholbert
  • Re: Intent to unship: -moz-prefixed CSS gradient functions Daniel Holbert
• Straw man mozilla-central node_modules policies; comments requested dmosedale
• Firefox Performance Profiling Workshop in Mozlando Harald Kirschner
• Intent to unship xml:base Jonathan Kingston
  • Re: Intent to unship xml:base Jonathan Kingston
• Soft code freeze for Firefox 65 starts December 3 Ryan VanderMeulen
  • Re: Soft code freeze for Firefox 65 starts December 3 Ryan VanderMeulen
• The upcoming C/C++ coding style change Sylvestre Ledru
  • Re: The upcoming C/C++ coding style change Boris Zbarsky
  • Re: The upcoming C/C++ coding style change Ehsan Akhgari
  • Re: The upcoming C/C++ coding style change Boris Zbarsky
  • Re: The upcoming C/C++ coding style change Ehsan Akhgari
  • Re: The upcoming C/C++ coding style change Boris Zbarsky
  • Re: The upcoming C/C++ coding style change Ehsan Akhgari
  • Re: The upcoming C/C++ coding style change Boris Zbarsky
  • Re: The upcoming C/C++ coding style change Randell Jesup
  • Re: The upcoming C/C++ coding style change Jonathan Kew
  • Re: The upcoming C/C++ coding style change Randell Jesup
  • Re: The upcoming C/C++ coding style change Ehsan Akhgari
  • Re: The upcoming C/C++ coding style change Randell Jesup
  • Re: The upcoming C/C++ coding style change Honza Bambas
  • Re: The upcoming C/C++ coding style change Ehsan Akhgari
  • Re: The upcoming C/C++ coding style change Honza Bambas
  • Re: The upcoming C/C++ coding style change Ehsan Akhgari
  • Re: The upcoming C/C++ coding style change Andrew McCreight
  • Re: The upcoming C/C++ coding style change Emilio Cobos Álvarez
  • Re: The upcoming C/C++ coding style change Ehsan Akhgari
  • Re: The upcoming C/C++ coding style change Emilio Cobos Álvarez

• Earlier messages
• Later messages