Re: Intent to implement/ship: Support for msApplication-TileImage/Color

2014-08-04 Thread Florian Bender
Am Montag, 4. August 2014 20:39:34 UTC+2 schrieb Wesley Johnston:
 I have never seen this! Seems like something we could use. i.e. we would 
 still need a logo designed to be shown against the site color.

There is link[rel=icon] with sizes attribute (support for multiple sizes 
ongoing, don't have a bug, though, sorry!). There is also talk about supporting 
link[rel=apple-touch-icon], esp. for B2G. 
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: Intent to implement/ship: Support for msApplication-TileImage/Color

2014-08-03 Thread Florian Bender
Am Freitag, 1. August 2014 18:11:23 UTC+2 schrieb Wesley Johnston:
 Link to standard: There is no public standard in place for these meta-tags 
 and none in progress either. 

Have you seen https://github.com/whatwg/meta-theme-color ?
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: Intent to implement: webserial api

2014-08-03 Thread Florian Bender
Yeah, I think this should work for a first version. We can relax these 
restrictions in the future. 
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: Intent to implement: webserial api

2014-08-03 Thread Florian Bender
Am Dienstag, 15. Juli 2014 21:01:19 UTC+2 schrieb somb...@gmail.com:
 I think an important statement for the spec to make is why it needs to 
 exist at all?  Specifically, it seems like both the WebUSB 
 https://bugzil.la/674718 and WebBluetooth https://bugzil.la/674737 specs 
 should both be equally capable of producing the standard stream 
 abstractions supported by the protocols.

There are several ways to expose a serial port in addition to USB and BT. The 
WebSerial API shouldn't care about the transport layer. Neither does the OS, it 
just exposes the serial port which may or may not go through USB, BT, native 
interface, or whatever. It's similar to a WebIPP API: You don't want to know 
whether the printer is connected through USB, Parallel, cabled or wireless 
network, you just want the OS to take the route it was configured with and 
expose a common interface for all routes.
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: Intent to implement: Ability to surpress default contextmenu items

2014-07-01 Thread Florian Bender
Am Sonntag, 29. Juni 2014 03:53:21 UTC+2 schrieb Dale Harvey:
 however they are currently shown in addition to the default items, we are
 looking to implement an optional attribute that allows authors to disable
 the default context menu items so only the applications items are shown.

Please take a look at my proposal a while ago here: 
https://www.w3.org/Bugs/Public/show_bug.cgi?id=12999#c22 (There's more 
discussion in the Bug)

Please note that the current Firefox implementation of context menus does not 
follow the latest spec. This should probably be updated first. 

However, the longer I'm thinking about it, it'd be the best (IMHO) to not have 
declarative way to extend/modify the context menu, but instead have an API for 
that. One reason is that most applications of menu do not make much sense 
without having JS listening for events. Another is the different UI/UX concepts 
of mobile vs desktop, and it's very hard to handle this declaratively without a 
boatload of attributes which IMHO makes it too complex. 

I do have some simple ideas for an API, and once my thesis is finished, I may 
take a shot at sketching up a spec. Will take a few weeks, though. 

Best regards
--fbender
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: Plug-in feature not available in the web platform. Alternatives?

2013-12-01 Thread Florian Bender
Am Mittwoch, 20. November 2013 20:11:17 UTC+1 schrieb fma spew:
 And btw, is WebCrypto an only-Mozilla thing?
 

No: http://www.w3.org/TR/WebCryptoAPI/ (work in progress)

(Though Mozilla has proprietary extensions: 
https://developer.mozilla.org/en-US/docs/JavaScript_crypto – but be aware that 
these may be dropped in the nera future!)
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: A static analyzer found 3 potential security bugs in our code

2013-10-30 Thread Florian Bender
Shouldn't this be posted to m.d.security?
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: Removal of native notification systems on desktop platforms

2013-10-28 Thread Florian Bender [:fbender]
Mac OS X Mavericks has been released with improvements to NC. Safari uses NC to 
display Web/PushNotifications and seems to work quite well. 

I'd like you to revisit the decision to drop NC in favor of XUL Notifications, 
and have a second look at the new API and capabilities. NC support could be 
limited to 10.9 to reduce maintenance cost (luckily, nearly everyone is 
eligible for the free update which means that earlier versions could fade into 
irrelevance sooner than later), and keep the XUL Notifications for 10.6-10.8 
(as long as these versions are supported and have a meaningful market share). 
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform