Bugzilla has defaulted to marking new bugs as status-firefoxXX: affected.
I'm not sure when it started but this is why.
Hope that helps,
Jared
On Sat, May 30, 2015 at 11:58 AM, Philip Chee wrote:
> Why are these SeaMonkey bugs flagged status-firefox41: affected
>
> https://bugzilla.mozilla.org/
We should consider a series of fallbacks for this internal API.
The metadata story for things like icon, title, description, hero images, is
complicated. Implementation in the follows real-world use cases like posting
rich snippets to Facebook or getting an image to show up on Twitter, rather
t
We should use whatever formats people are using to mark up pages. If that
is microdata we should use that. If it's RDF we should use that. If its
JSONLD we should use that.
The API that is used to extract the data is irrelevant. That will be an
internal API anyway. Effectively we should think of t
On 29/05/2015 22:31, ISHIKAWA, Chiaki wrote:
> I figured out the particular cause of
> test-cloudfile-backend-hightail.js.
> experienced during |make mozmill| when I simulated "short read" and
> "short write" to files
> under the profile directory used by the test was that
> *.db files managed by
Why are these SeaMonkey bugs flagged status-firefox41: affected
https://bugzilla.mozilla.org/buglist.cgi?f1=cf_status_firefox41&list_id=12290852&o1=anyexact&query_format=advanced&f2=OP&v1=affected&product=SeaMonkey
Why are these SeaMonkey bugs flagged status-firefox40: affected
https://bugzilla.mo
On 30 May 2015 at 00:56, Anne van Kesteren wrote:
> We've bitten ourselves before going down the RDF rathole (see
> extensions et al). Not sure we should so rapidly start again. Why
> can't you use the Microdata API?
>
Is this already supported in Gecko? I can't find it documented anywhere,
exce
6 matches
Mail list logo
