Re: Intent to remove: Ability to specify the Raanana macOS system font by its Hebrew name in CSS

2017-01-17 Thread Jet Villegas
* Including a special-case check for the name Raanana when enumerating > the system fonts > My preference as well, though I'm not convinced it's worth doing. The Wikipedia page for the city of Ra'anana [0] marks up the city's Hebrew name as: רַעֲנָנָה‎ The Hebrew version [1] doesn't specify

Intent to remove: Ability to specify the Raanana macOS system font by its Hebrew name in CSS

2017-01-17 Thread Henri Sivonen
I'm in the process of rewriting our encoding converter infrastructure in Rust. For a new implementation, it makes sense to support only the Web-exposed encodings, that is, the encodings specified in the Encoding Standard. Currently, Firefox supports decoding non-Encoding Standard encodings in one

Re: Intent to implement and ship: URLSearchParams from array or object

2017-01-17 Thread smaug
So we'll get support for object too in FF53, not only array? On 01/17/2017 07:11 PM, Andrea Marchesini wrote: Summary: URLSearchParams constructor is changed in the latest URL spec. Now it's possible to create URLSearchParams objects starting from a string, an array and from an object. Bugs:

Re: Deprecating XUL in new UI

2017-01-17 Thread smaug
On 01/18/2017 08:28 AM, smaug wrote: On 01/17/2017 10:51 PM, J. Ryan Stinnett wrote: On Mon, Jan 16, 2017 at 3:08 PM, smaug wrote: On 01/16/2017 10:43 PM, Dave Townsend wrote: One of the things I've been investigating since moving back to the desktop team is how we can

Re: Is it possible to implement "click to play" for Adobe Flash in XULRunner app?

2017-01-17 Thread 段垚
Thank you very much! It looks a bit complicated. Maybe I'd consider a pure front-end solution instead. 在 2017/1/14 0:06, Benjamin Smedberg 写道: You have to manage the UI yourself. Firefox does this with a combination of applying an overlay to the disabled Flash which shows the grey UI, plus

Re: Deprecating XUL in new UI

2017-01-17 Thread smaug
On 01/17/2017 10:51 PM, J. Ryan Stinnett wrote: On Mon, Jan 16, 2017 at 3:08 PM, smaug wrote: On 01/16/2017 10:43 PM, Dave Townsend wrote: One of the things I've been investigating since moving back to the desktop team is how we can remove XUL from the application as much as

Re: Deprecating XUL in new UI

2017-01-17 Thread smaug
On 01/17/2017 12:05 AM, Dave Townsend wrote: Trees! I knew I was forgetting something, thank you. Yeah those are things we're going to need some sane replacements for. AS far as XBL goes, while I suspect it works from HTML documents I think we want to be phasing out use of XBL too for pretty

Emoji and Bugzilla

2017-01-17 Thread Emma Humphries
As the BMO team announced earlier, we're going to be allowing emoji in user inputs in Bugzilla. https://bugzilla.mozilla.org/show_bug.cgi?id=1253535 We have not committed to a date to release this feature as it requires a production database change which we haven't been able schedule yet.

Re: Deprecating XUL in new UI

2017-01-17 Thread Gijs Kruitbosch
On 17/01/2017 17:55, Bobby Holley wrote: On Tue, Jan 17, 2017 at 8:56 AM, Boris Zbarsky wrote: On 1/16/17 4:28 PM, Matthew N. wrote: Does it just work from XHTML documents? Yes, as far as I know. Is our implementation of Web Components ready to replace it and riding

Re: Deprecating XUL in new UI

2017-01-17 Thread Brian Grinstead
A few things we had to handle when going through this process for the devtools UI: 1) Already mentioned to but for panels we added a new module that falls back to XUL panels for now 2) For context menu handling we we added a new module similar to the Menu API from Electron that falls back to

Re: Deprecating XUL in new UI

2017-01-17 Thread Kris Maglione
On Tue, Jan 17, 2017 at 02:51:47PM -0600, J. Ryan Stinnett wrote: I am not very familiar with the details of XUL prototype cache, but my understanding of bug 1286082[1] is that currently the XUL prototype cache is not actually working correctly (and possibly has been broken since bug 592943[2]

Re: Deprecating XUL in new UI

2017-01-17 Thread J. Ryan Stinnett
On Mon, Jan 16, 2017 at 3:08 PM, smaug wrote: > On 01/16/2017 10:43 PM, Dave Townsend wrote: >> >> One of the things I've been investigating since moving back to the desktop >> team is how we can remove XUL from the application as much as possible. >> The >> benefits for doing

Re: Deprecating XUL in new UI

2017-01-17 Thread J. Ryan Stinnett
On Mon, Jan 16, 2017 at 2:43 PM, Dave Townsend wrote: > * iframe elements don't have the same capabilities that the XUL browser > element does and we use that in some UI. We do have available to chrome pages on desktop now (bug 1238160[1], landed in Firefox 47), which

Re: Deprecating XUL in new UI

2017-01-17 Thread Jaroslav Šnajdr
Hello Boris, you're right - it's not XUL/HTML difference, but a chrome/content one. The issue with React and privileged iframes was investigated here: https://bugzilla.mozilla.org/show_bug.cgi?id=1245921#c55 see comments 55 and on. Jarda On Tue, Jan 17, 2017 at 6:05 PM, Boris Zbarsky

Re: Deprecating XUL in new UI

2017-01-17 Thread Bobby Holley
On Tue, Jan 17, 2017 at 8:56 AM, Boris Zbarsky wrote: > On 1/16/17 4:28 PM, Matthew N. wrote: > >> Does it just work from XHTML documents? >> > > Yes, as far as I know. > > Is our implementation of Web Components ready to replace it and riding the >> trains? >> > > No. >

Intent to implement and ship: URLSearchParams from array or object

2017-01-17 Thread Andrea Marchesini
Summary: URLSearchParams constructor is changed in the latest URL spec. Now it's possible to create URLSearchParams objects starting from a string, an array and from an object. Bugs: https://bugzilla.mozilla.org/show_bug.cgi?id=1330678

Re: Deprecating XUL in new UI

2017-01-17 Thread Boris Zbarsky
On 1/16/17 4:31 PM, Jaroslav Šnajdr wrote: - there is a difference in how events are dispatched in HTML vs XUL iframes. In HTML, the capture/bubble phases are isolated inside the iframe window, but in XUL, the target chain crosses the iframe boundaries. I'm not aware of this behavior for XUL,

Re: Deprecating XUL in new UI

2017-01-17 Thread Boris Zbarsky
On 1/16/17 4:28 PM, Matthew N. wrote: Does it just work from XHTML documents? Yes, as far as I know. Is our implementation of Web Components ready to replace it and riding the trains? No. -Boris ___ dev-platform mailing list

Re: Deprecating XUL in new UI

2017-01-17 Thread Brian Grinstead
You can still use dtd files in XHTML as long as it’s chrome-privileged. A lot of the about pages are doing this (aboutNetError.xhtml and others: https://dxr.mozilla.org/mozilla-central/search?q=path%3Axhtml+dtd). Brian > On Jan 17, 2017, at 3:34 AM, zbranie...@mozilla.com wrote: > > One more

Re: Deprecating XUL in new UI

2017-01-17 Thread zbraniecki
One more thing that XUL gives us is L10n. With HTML, we can use .properties to load localization resources and inject them into HTML, but I believe this to be a very inelegant solution with a surprisingly high risk of bugs. We do have an l10n framework called L20n that is supposed to replace