Re: Linked Data must die. (was: Linked Data and a new Browser API event)
Let me start by saying I don't care which format we use. (Formats come, and formats go.) I do care, however, that my use case is supported. My use case, speech enabling web apps and web pages for Firefox OS's voice assistant Vaani, requires that the chosen format support something akin to schema.org's actions[1] as well as the ability for anyone to add custom actions. This use case is also required by the Taipei team working on the Firefox OS TV. Open Graph[2] does not support such actions. Thus, it is not sufficient for our use case. (Facebook extended Open Graph with actions[3]. However, the set of valid actions is completely under Facebook's control which makes their Open Graph extension a non-starter.) Microdata[4], RDFa[5], and JSON-LD[6] do support actions. Hence, support for at least one of these is sufficient for our use case. Microformats[7] currently does not support actions. Hence, it is not sufficient for our use case. The Vaani team and the Taipei team working on the Firefox OS TV would love to base our work on that being done for pinning the web. (One of the 3 virtues of a programmer *is* laziness.) However, if neither Microdata, RDFa, nor JSON-LD is supported, we will, unfortunately, be forced to go our own way. [1] http://schema.org/Action [2] http://ogp.me/ [3] https://developers.facebook.com/docs/sharing/opengraph/using-actions [4] http://www.w3.org/TR/microdata/ [5] http://www.w3.org/TR/xhtml-rdfa-primer/ [6] http://www.w3.org/TR/json-ld/ [7] http://microformats.org/wiki/Main_Page ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Intent to Ship: Cache API
For the record, this landed in time for 41 here: https://hg.mozilla.org/mozilla-central/rev/f71f5a88e16d On Thu, Jun 18, 2015 at 11:41 AM, Benjamin Kelly bke...@mozilla.com wrote: Next week I plan to enable the Cache API by default. It has been developed behind the dom.caches.enabled pref. This pref has been enabled by default on nightly and aurora since FF39. Next week I plan to remove the pref completely so the feature will ride the trains to release. The Cache API is currently shipping in Chrome. Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1110144 Standard: https://slightlyoff.github.io/ServiceWorker/spec/service_worker/index.html#cache-objects MDN docs: https://developer.mozilla.org/en-US/docs/Web/API/CacheStorage Please let me know if there are any questions or concerns. Thank you. Ben ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Announcing the Content Performance program
Nathan, it looks like the SessionRestore feature that was causing test failures has been removed by Tim in the meantime… Does that mean that the 'possible webcompat issues’ is the only real issue left? If so, I’d suggest to request feedback from :annevk and/ or :dbaron (for example) to get a feel for it, because your work in that bug looks too good to let go! Cheers, Mike. On 29 Jun 2015, at 02:14, Nathan Froyd nfr...@mozilla.com wrote: On Sun, Jun 28, 2015 at 5:23 PM, Mike Hommey m...@glandium.org wrote: BTW, wasn't there an effort a few couple years ago, to move content event loop in different threads for different tabs? What happened to that? If you are referring to bug 715376 (and related), those patches are still in my queue, fully rebased. We only need to decide that it's worth spending a significant amount of time addressing the test failures induced by those patches (see comment 109 in that bug, for instance) and the possible webcompat issues from those patches. -Nathan ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Announcing the Content Performance program
On Sun, Jun 28, 2015 at 5:14 PM, Nathan Froyd nfr...@mozilla.com wrote: On Sun, Jun 28, 2015 at 5:23 PM, Mike Hommey m...@glandium.org wrote: BTW, wasn't there an effort a few couple years ago, to move content event loop in different threads for different tabs? What happened to that? If you are referring to bug 715376 (and related), those patches are still in my queue, fully rebased. We only need to decide that it's worth spending a significant amount of time addressing the test failures induced by those patches (see comment 109 in that bug, for instance) and the possible webcompat issues from those patches. It is awesome to hear that you have those patches rebased. I really hope we push forward with that. In addition to the potential benefits listed in that bug, the JS debugger currently has a lot of issues where suppressing a page's events doesn't actually suppress everything (Promises, postMessage, XHR, I think a couple others) and so JS can still run while you are paused. Being able to use a debugger/chrome dedicated event queue would nicely solve all these cases in one swoop. See https://bugzilla.mozilla.org/show_bug.cgi?id=1074448 for more. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Linked Data must die. (was: Linked Data and a new Browser API event)
On June 27, 2015 at 10:02:47 AM, Anne van Kesteren (ann...@annevk.nl) wrote: The data I have does not back this up, Microdata is shown to be growing fast whereas Microformats usage has remained relatively stable. Also, we didn't find Microformats usage on any of the example high profile sites we used during prototyping, it seems to be more commonly used on Wordpress blogs and Indie Web style web sites. Could we see some examples of the cards you are generating already with existing data from the Web (from your prototype)? The value is really in seeing that users will get some real benefit, without expecting developers to add additional metadata to their sites. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
FYI: Change in crash signature naming in crash-stats
There has been a change in how Socorro records crash signatures. All signature pieces between and are now collapsed into T. That means that some crashes look like they stopped on June 12, when they really have not. Please be on the lookout for this as you interpret crash-stats. Here's the Socorro bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1163831 Example of this resulting in crash looking oddly fixed : https://bugzilla.mozilla.org/show_bug.cgi?id=1167557 This should be affecting tools built to identify significant crashes. It also means that people looking at particular crash signatures to verify if a crash sig has disappeared (often the best verification we can manage for a crash bug) or is getting worse. Best, Liz -- Liz Henry (:lizzard) lhe...@mozilla.com ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: [feature] open certain domains into a private window
For Android, we have been discussing building a feature like this around tab queues (the new open later feature we've been working on), but I don't know of any desktop plans for something like this. I agree the UX/product work around this idea could be tricky, so I'm not sure dev-platform is the right place for this discussion. I would encourage you to talk to Javaun about new ideas for private browsing, since he's the product manager leading our private browsing 2.0 initiative. Margaret On Wed, Jun 24, 2015 at 4:31 PM, Ehsan Akhgari ehsan.akhg...@gmail.com wrote: On 2015-06-23 8:57 PM, Andreas Tolfsen wrote: On 23 Jun 2015, at 20:24, Karl Dubost kdub...@mozilla.com wrote: Le 23 juin 2015 à 19:16, Eric Shepherd esheph...@mozilla.com a écrit : I thought we had an open in new private window option when right clicking links. Not a total solution but helps. My I'm reading an email with a link to Google Doc was assuming an email client (not webmail), could be IRC, or anything else outside of the browser. Is it an option to register two browser handlers in the operating system for Firefox? One for regular Firefox, and one for Firefox in private mode? We already have that, but that won't help for Karl's use case. The technical work involved in fixing what Karl is asking for is simple. The UX we want to expose the feature through is the more interesting question IMO. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Announcing the Content Performance program
I'm a big fan of it working, because I believe that it's a key component to handling correctly slow scripts. Cheers, David On 29/06/15 02:14, Nathan Froyd wrote: If you are referring to bug 715376 (and related), those patches are still in my queue, fully rebased. We only need to decide that it's worth spending a significant amount of time addressing the test failures induced by those patches (see comment 109 in that bug, for instance) and the possible webcompat issues from those patches. -Nathan -- David Rajchenbach-Teller, PhD Performance Team, Mozilla signature.asc Description: OpenPGP digital signature ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Linked Data must die. (was: Linked Data and a new Browser API event)
On June 29, 2015 at 7:07:33 AM, Michael Henretty (mhenre...@mozilla.com) wrote:
We will definitely start with the simple open graph stuff that Ted
mentioned (og:title, og:type, og:url, og:image, og:description)
since they are so widely used. And yes, even these simple ones are
problematic. For instance, when navigating between dailymotion videos they
keep the current meta tags, and just updates the html body content. In
fact, single-page-apps in general are hard here. Also, on the mobile
version of youtube they leave out og tags entirely, probably as a
performance optimization. Turns out, many sites do this. So in 2.5 we will
have to account for all of this and the solution might not be pretty.
ok, it's good to see you've already started to encounter the issues.
I think Microformats addresses the aforementioned problems.
They might, though they can also change from under you in fun ways, or be
invalid/incorrect.
But if youtube,
wikipedia, pinterest, twitter, facebook, tumblr, etc don't use them widely
what is the point of supporting them in a moz-internal API? Let's be
pragmatic and start with og. What's the next biggest win for us? Is the
data clear? Ben seems to think JSON-LD [1], does anyone have data to the
contrary?
I don't have data, just some graying hair and warnings from the distant past
[1]. You've all seen already how controversial these formats are, and hopefully
you understand why now (expecting validity/sanity from the web is a non-starter
- it's the fallacy of the semantic web, and why we mockingly call it the
pedantic web and recoil in horror and lash out with rage at the mere mention
of it).
So flip the problem a bit: what you actually want is just simple data that can
be transformed into a card, right? basically, we scrape some text values from a
HTML page and you just put it into a different HTML document: the card.
As long as you don't expect validity of that data (i.e., you don't expect a
standards conforming JSON-LD, RDFa, microdata, microformat, whatever parser*)
then that frees us to build some kind of HTML Scraper that is actually built
for purpose (one that is fault tolerant, and basically doesn't give a crap what
the RDFa or JSON-LD spec says, but is designed to aggressively find the data
you need to build nice cards). This is also why I suggest you start with og:
data, because it basically takes the same approach: it doesn't give a crap what
the RDFa spec says (and neither do developers that add it to their pages, as
I'm sure you've already seen), it just defines some things by using some HTML
elements that kinda-sorta looks like RDFa. However, it comes with a ton of
problems which you will have a great time trying to deal with as you build the
pinned-sites feature. The same with Twitter's card format.
At the end of the day, what Gecko should be passing back is a simple JS object
that contains:
{
og: {... name/value pairs...}
twitter: {... name/value pairs...}
other_because_we_can_add_new_things_as_needed_yay: {... name/value pairs...}
}
If we are not going to be doing any semantic inferencing on that data or
actually doing the linked data part, then we don't need a JSON-LD
representation of it. We just need a fairly simple structure from which FxOS
can build different cards. That avoids talk of supporting controversial formats
like JSON-LD and RDFa, while actually supporting web content: in the sense
that, we are just pulling this 'og' meta stuff from the page, we don't care
what it is.
My 2c,
[1] Warning from 2003, that the same things happened with RSS. They had to
abandon XML:
http://www.xml.com/pub/a/2003/01/22/dive-into-xml.html
I know, I know, this is how HTML got to be tag soup: browsers that never
complained. Now the same thing is happening in the RSS world because the same
social dynamics apply. End users who can't even spell XML certainly don't
care about silly little formatting rules; they just want to follow their
favorite sites in their news aggregator. When 10% of the world's RSS feeds are
not well-formed -- including some high-profile feeds that thousands of people
want to read -- the ability to parse ill-formed feeds becomes a competitive
advantage. (And if you think the same thing won't happen when RDF and the
Semantic Web go mainstream, you're deluding yourself. The same social dynamics
apply. Boy, is that going to be messy.)
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
[Firefox Desktop] Issues found: June 22nd to June 26th
Hi everyone, You can find below the list of new issues found and filed by the Desktop Manual QA team last week (Week 26: June 22 - June 26). Additional details on the team's priorities last week, as well as the plans for the current week can be found at: https://etherpad.mozilla.org/DesktopManualQAWeeklyStatus. Release Channel: No bugs. Beta Channel: NEW Bug https://bugzilla.mozilla.org/show_bug.cgi?id=1176684 1176684 - Hello button turns blue without anyone joining the conversation * Regression: No. * Severity: Normal. NEW Bug https://bugzilla.mozilla.org/show_bug.cgi?id=1176692 1176692 - [Windows] Clicking one of the options from the Forget button places a focus ring on it * Regression: No. * Severity: Minor. NEW Bug https://bugzilla.mozilla.org/show_bug.cgi?id=1176837 1176837 - crash in OOM | large | mozalloc_abort(char const* const) | mozalloc_handle_oom(unsigned int) | moz_xmalloc | std::allocatorT::allocate(unsigned int) * Regression: No. * Severity: Critical. NEW Bug https://bugzilla.mozilla.org/show_bug.cgi?id=1176841 1176841 - [Linux] Low quality image on google maps earth mode. * Regression: No. * Severity: Normal. NEW Bug https://bugzilla.mozilla.org/show_bug.cgi?id=1176851 1176851 - Reader mode offered on https://startpage.com/ * Regression: Yes - since 39 Beta 4. * Severity: Normal. NEW Bug https://bugzilla.mozilla.org/show_bug.cgi?id=1177348 1177348 - Video driver is crashed by Tab Sharing * Regression: No. * Severity: Major. NEW Bug https://bugzilla.mozilla.org/show_bug.cgi?id=1177360 1177360 - Amazon page incorrect displayed in Reader View Mode * Regression: No. * Severity: Normal. Aurora Channel: RESO Bug https://bugzilla.mozilla.org/show_bug.cgi?id=1176683 1176683 - crash in mozilla::a11y::HyperTextAccessible::LandmarkRole() const * Regression: No. * Severity: Critical. NEW Bug https://bugzilla.mozilla.org/show_bug.cgi?id=1177046 1177046 - Blank Hello panel while mouse over Featured Themes via Add-ons Manager - Get Add-ons tab * Regression: No. * Severity: Normal. NEW Bug https://bugzilla.mozilla.org/show_bug.cgi?id=1177079 1177079 - crash in libdrm_nouveau.so.2.0.0@0x2ff2 * Regression: No. * Severity: Critical. NEW Bug https://bugzilla.mozilla.org/show_bug.cgi?id=1177091 1177091 - Ugly artifacts when entering video fullscreen * Regression: No. * Severity: Normal. NEW Bug https://bugzilla.mozilla.org/show_bug.cgi?id=1177372 1177372 - White glitch visiting ted.com * Regression: No. * Severity: Normal. Nightly Channel: NEW Bug https://bugzilla.mozilla.org/show_bug.cgi?id=1176661 1176661 - [HiDPI] Global indicator does not update size correctly if call is active * Regression: No. * Severity: Normal. NEW Bug https://bugzilla.mozilla.org/show_bug.cgi?id=1176664 1176664 - [Mac] Not now option from Add-on Restart doorhanger is bigger than the other buttons * Regression: No. * Severity: Normal. NEW Bug https://bugzilla.mozilla.org/show_bug.cgi?id=1176690 1176690 - Misaligned elements in Available Updates tab from Add-ons Manager * Regression: No. * Severity: Normal. ESR Channel: NEW Bug https://bugzilla.mozilla.org/show_bug.cgi?id=1177382 1177382 - Error is thrown by controller.jsm each time a URL is dragged onto the Bookmarks Toolbar * Regression: Yes - since 2014-11-14. * Severity: Normal. NEW Bug https://bugzilla.mozilla.org/show_bug.cgi?id=1177385 1177385 - pdf.js's controls are also affected by the zooming actions initiated from the menu * Regression: -. * Severity: Normal. NEW Bug https://bugzilla.mozilla.org/show_bug.cgi?id=1177681 1177681 - Trouble resuming webm video from homepage * Regression: -. * Severity: Normal. Regards, Florin. Florin Mezei | QC Team Lead SOFTVISION | 57 Republicii Street, 400489 Cluj-Napoca, Romania Email: mailto:fme...@softvision.ro fme...@softvision.ro | Web: http://www.softvision.ro/ www.softvision.ro The content of this communication is classified as SOFTVISION Confidential and Proprietary Information. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Linked Data must die. (was: Linked Data and a new Browser API event)
On Saturday, June 27, 2015, Benjamin Francis bfran...@mozilla.com wrote: On 26 June 2015 at 19:25, Marcos Caceres mar...@marcosc.com javascript:_e(%7B%7D,'cvml','mar...@marcosc.com'); wrote: Could we see some examples of the cards you are generating already with existing data from the Web (from your prototype)? The value is really in seeing that users will get some real benefit, without expecting developers to add additional metadata to their sites. The prototype only supports Open Graph, you can see some example cards in this video Pinning the Web - Prototoype https://www.youtube.com/watch?v=FiLnRoRjD5k These look fantastic! so why not start with just those? Or are all those card types done and thoroughly tested on a good chunk of Web content? As I mentioned before, I'd be worried about the amount of error recovery code that will be needed just for those types of cards. (Sorry, I don't know any of the background and if you've already dealt with this). ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Linked Data must die. (was: Linked Data and a new Browser API event)
Thanks for the responses, Let me reiterate the Product requirements: 1. Support for a syntax and vocabulary already in wide use on the web to allow the creation of cards for the largest possible volume of existing pinnable content 2. Support for a syntax with a large enough and/or extensible vocabulary to allow cards to be created for all the types of pinnable content and associated actions we need in Gaia We need to deliver this by B2G 2.5 FL in September. *Existing Web Content* I think we're agreed that Open Graph gives us enough of a minimum viable product for the first requirement. However, it's not OK to just hard code particular og types into Gecko, we need to be able to experiment with cards for lots of different Open Graph types without having to modify Gecko every time (imagine system app addons with experimental card packs). Open Graph is just meta tags and we already have a mechanism for detecting specific meta tags in Gaia - the metachange event on the Browser API. As a minimum all we need to do to access Open Graph meta tags is to extend this event to include all meta tags with a property attribute, which is only used by Open Graph. We could go a step further and extend the event to all meta tags, which would also give us access to Twitter card markup for example, but that isn't essential. We do not need an RDFa parser for this, we can filter/clean up the data in the system app in Gaia where necessary (the system app is widely regarded to be part of the platform itself). *Gaia Content* Open Graph does not have a large enough vocabulary, or (as Kelly says) the ability to associate actions with content, needed for the second requirement. Schema.org has a large existing vocabulary which basically fulfils these use cases, though some parts are more tested than others, with examples given in Microdata, RDFa and JSON-LD syntaxes, eg: - Contact - http://schema.org/Person - Event - http://schema.org/Event - Photo - http://schema.org/Photograph - Song - http://schema.org/MusicRecording - Video - http://schema.org/VideoObject - Radio station - http://schema.org/RadioChannel - Email - http://schema.org/EmailMessage - Message - http://schema.org/Comment Schema.org also provides existing schemas for actions associated with items (https://schema.org/docs/actions.html), although examples are only given in JSON-LD syntax. Schema.org is just a vocabulary and Tantek tells me it's theoretically possible to express this vocabulary in Microformats syntax too - it's possible to create new vendor prefixed types, or suggest new standard types to be added to the Microformats wiki. This would be required because Microformats does not have a big enough existing vocabulary for Gaia's needs. Microdata, RDFa and JSON-LD use URL namespaces so are extensible by design with a non-centralised vocabulary (this is seen as a strength by some, as a weakness by others). The data we have [1][2][3][4] shows that Microdata, then RDFa (sometimes considered to include Open Graph), is used by the most pinnable content on the web, but the data does not include all modern Microformats. We also don't have any data for JSON-LD usage. However, existing usage is not the most important criteria for the second requirement, it's how well it fits the more complex use cases in Gaia (and how much work it is to implement). There is resistance to implementing a full Microdata or RDFa parser in Gecko due to its complexity. JSON-LD is more self-contained by design (for better or worse) and could be handed over to the Gaia system app directly via the Browser API without any parsing in Gecko. Microformats is possibly less Gecko work to implement than Microdata or RDFa, but more than JSON-LD. *Conclusions* My conclusion is that the least required work in Gecko for the highest return would be: 1. *Open Graph* (bug 1178484) - Extending the existing metachange Browser API event to include all meta tags with a property attribute. This would allow Gaia to add support for all of the Open Graph types, fulfilling requirement 1. 2. *JSON-LD* (bug 1178491) - Adding a linkeddatachange event to the Browser API which is dispatched by Gecko whenever it encounters a script tag with a type of application/ld+json (as per the W3C recommendation [5]), including the JSON content in the payload of the event. This would allow the Gaia system app to support existing schema.org schemas (including actions), with the least amount of work in Gecko, and already in a JSON format it can store directly in the Places database (DataStore/IndexedDB). Kan-Ru is the owner of the Browser API module in Gecko and has said he's happy with this approach and is happy to review the code. Let's go ahead with that now, unblocking the work on the Gaia side. (Note that I have no intention of building a full RDF style parser in Gaia, we'll just extract the data we need from the JSON, for the good reasons that
Intent to ship Notification API on Web Workers
Hello, Target release: Firefox 41 Implementation and shipping bug: https://bugzilla.mozilla.org/buglist.cgi?quicksearch=916893 Specification: https://notifications.spec.whatwg.org/ Gecko already implements support for the Notification API on window behind the dom.webnotifications.enabled pref, and this has been enabled by default for at least a year. This is the intent to ship the same API on workers, guarded by the same pref, so it will be enabled by default. The patches landed on central on July 29, 2015. These patches implement support for the Notification constructor on dedicated and shared workers. This is exposed via the Notification constructor. The Service Worker parts of the Notification API are not shipping yet due to breaking some Gaia tests. That implementation is tracked in https://bugzilla.mozilla.org/show_bug.cgi?id=1114554 Potential for abuse? This API allows workers to abuse the user. There are some safeguards in place. 1) Notification.requestPermission() which prompts the user to grant permission is only available on window. This means the website cannot secretly acquire permission. It is also clear to the user which origin is requesting the permission. 2) Each notification displays the origin it came from. The user can revoke permission using the standard user agent mechanisms (Page Info in Firefox). Platforms: All platforms. Support in other engines: Blink - shipped - https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/4WNnq8BIydI Webkit - I don't have a way to try this out, but from the Blink intent to ship, it seems it isn't supported. Edge/Trident: not supported Developer documentation: https://developer.mozilla.org/en-US/docs/Web/API/Notification/Notification, the doc has not been updated for worker support yet. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
How create a full copy of mozbuild and dependencies at https://github.com/html-shell/mozbuild
I think doing this can getting mozbuild can be used as a independent software without the gecko source tree. -- 此致 礼 罗勇刚 Yours sincerely, Yonggang Luo ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
