During our last meeting we all seemed to agree on that defining/implementing
order for style-sheets is imports is super hard (if possible) and will bring
more
pain than it's worth for the web (aka. let's not make an already
over-complicated
system twice as complicated for very little benefits).
A couple of us at Mozilla have been trying to figure out how to revive
activities/intents for the web. Both work relatively well in closed
environments such as Firefox OS and Android, but seem harder to deploy
in a generic way on the web.
What we've been looking at instead is solving a smaller
On Mon, Nov 3, 2014 at 7:28 AM, Gabor Krizsanits
gkrizsan...@mozilla.com wrote:
During our last meeting we all seemed to agree on that defining/implementing
order for style-sheets is imports is super hard (if possible) and will bring
more
pain than it's worth for the web (aka. let's not make
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27222
Bug ID: 27222
Summary: [Shadow]: title attribute should inherit in shadow
DOM
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: All
Follow-up: there was an issue for meta-data already on the Github.
https://github.com/w3c/push-api/issues/81
Please, think of the resources and be webby to one another.
Cheerio,
rektide
On Mon, Oct 27, 2014 at 10:55:40AM -0400, rekt...@voodoowarez.com wrote:
Hello. I heard Push is finally in
I know this is probably the wrong place/time to say this, but fwiw, a
primary use case for imports is replacing:
script src=my-lib/my-lib.js/script
!-- the script above might have some HTML in it, encoded as a string,
comment, or other hack --
!-- the script above may load additional dependencies
