Re: Minimum viable custom elements
On Sat, Jan 31, 2015 at 5:58 AM, fantasai fantasai.li...@inkedblade.net wrote: -webkit-appearance: none isn't a proprietary extension, it's a prefixed version of something that was once in a standards-track document. It got removed because there were serious design problems with the original idea, but some values stuck around. I don't see how that makes it any less proprietary. Unless some body is standardizing '-webkit-appearance', prefix et al, my point stands. -- https://annevankesteren.nl/
Re: Minimum viable custom elements
On Sat, Jan 31, 2015 at 8:25 AM, Tantek Çelik tan...@cs.stanford.edu wrote: I'm tracking the state of requests for 'appearance' here: https://wiki.csswg.org/spec/css4-ui#appearance Feel free to directly edit that wiki page and add more concrete data / research that you think will help make a decision in terms of design etc. For now, there is insufficient data to show anyhing of any reasonable interop for this property, hence it is still postponed at best. I suspect the main reason for that to be that the specification is not detailed enough and there not being a test suite. Have you checked with implementers? -- https://annevankesteren.nl/
Re: Minimum viable custom elements
On Fri, Jan 30, 2015 at 7:22 PM, Alice Boxhall aboxh...@google.com wrote: Sure, that works for this example (which was created in a huge rush at the last minute before a talk, like probably 90% of my productive work), but I don't believe it wouldn't work for http://www.polymer-project.org/components/paper-radio-button/demo.html which has a fancy animation for changing states. That example seems to depend on another proprietary extension: -webkit-tap-highlight-color. I can't find anything else that would be responsible for the effect. So, I naively ask, what's stopping us from standardising something like -webkit-appearance: none? Someone has to put in the work. -- https://annevankesteren.nl/
Re: [clipboard API] platform integration stuff - in spec or out of scope?
On 31 janv. 2015, at 14:48, Hallvord Reiar Michaelsen Steen hst...@mozilla.com wrote: If yes, do any of the other mandatory types have gotchas like Windows HTML Format - on any platform? The mandatory types currently are: text/plain text/uri-list text/csv text/css text/html application/xhtml+xml image/png image/jpg, image/jpeg image/gif image/svg+xml application/xml, text/xml application/javascript application/json application/octet-stream I don't know what these map to on platforms that do not use MIME types to describe clipboard contents. Should this information be dug up and included? First request: can we add the three MathML media-types? (those are: application/mathml-presentation+xml, application/mathml-content+xml, application/mathml+xml) I think I could help dig the names out by looking at the following documents: - http://developer.apple.com/mac/library/documentation/FileManagement/Conceptual/understanding_utis/ - https://msdn.microsoft.com/en-us/library/system.windows.dataformats.aspx Also, some specs and media-type-registration RFCs indicate the names in the native formats. I think this would be the right place to hunt too (I know that MathML and SVG do). Probably it'll never be complete (e.g. I do not think application/octet-stream can have a name on clipboards). Shall I just make the suggestions as a table per (html?) mail? paul
Re: [clipboard API] platform integration stuff - in spec or out of scope?
I don't know what these map to on platforms that do not use MIME types to describe clipboard contents. Should this information be dug up and included? First request: can we add the three MathML media-types? I know you've brought this up before, I haven't done anything about it and it's partly because I'm not actually sure myself what an implementation would have to do to support a data type.. I think I could help dig the names out by looking at the following documents: That would be absolutely terrific Paul - maybe make a wiki page or etherpad somewhere? It would really help me - coming more from the JavaScript side of things I can figure out and describe how all the JavaScript stuff works, but it's much harder to determine how the platform side needs to be specified. - http://developer.apple.com/mac/library/documentation/FileManagement/Conceptual/understanding_utis/ - https://msdn.microsoft.com/en-us/library/system.windows.dataformats.aspx Also, some specs and media-type-registration RFCs indicate the names in the native formats. I think this would be the right place to hunt too (I know that MathML and SVG do). Probably it'll never be complete (e.g. I do not think application/octet-stream can have a name on clipboards). So.. If the most important platforms do not have a clipboard format or description for a specific MIME type, does that mean telling implementations to support it is meaningless? Sort of seems like it.. -Hallvord
