Knowledge Base discussions

Documentation Workshop #1 - Research

  1. Background: This is a workshop in our new Technical writing program. These are designed to guide participants though the entire documentation process. If you have suggestions for making this particular workshop better, please reply to this thread.

    Watch the video on YouTube (16min)

    Links in this video:

    What changes and new features will be visible to users in Firefox 19 (Desktop & Mobile)? Reply to this thread with your answers.

    <blockquote>'''Background:''' This is a workshop in our new [[Technical writing program]]. These are designed to guide participants though the entire documentation process. If you have suggestions for making this particular workshop better, please reply to this thread.</blockquote> ==[http://youtu.be/4UJYRm4zYTk Watch the video on YouTube] (16min)== Links in this video: *[https://twitter.com/firefoxnightly Firefox Nightly Twitter account] *[https://wiki.mozilla.org/Firefox/DeliveryMeetings Firefox coordination meeting] - Wednesdays at 11am PDT *[https://wiki.mozilla.org/Firefox/Flight_Tracking Release Tracking] *[https://etherpad.mozilla.org/latest-features-list Latest features etherpad] *[https://www.google.com/calendar/ical/sumo%40michaelverdi.com/private-21abf0328378e2f6eea13a9ab1e72b6e/basic.ics Firefox releases ICAL] *[https://bugzilla.mozilla.org/buglist.cgi?field0-0-0=flagtypes.name;value0-0-0=ui-review;bug_status=RESOLVED;bug_status=VERIFIED;product=Core;product=Firefox;product=Firefox%20for%20Android;product=Toolkit;chfieldfrom=2012-10-08;resolution=FIXED;chfieldvalue=FIXED;chfieldto=Now;chfield=resolution;type0-0-0=substring;query_format=advanced;list_id=5398345 Firefox 19 bugzilla query] '''What changes and new features will be visible to users in Firefox 19 (Desktop & Mobile)? Reply to this thread with your answers.'''
  2. One thing I didn't talk too much about in the video are features that ride the trains for a while. Sometimes we add a feature to Firefox and we don't release it when that version of Firefox moves from Beta to Release. Instead the feature may stay on the Beta train for an extra cycle (or 5).

    The main way to find out about these feature is the Product coordination meeting. Looking at the notes it seems things often get left out and listening in on the meeting gives you more information. Another place to find out about these features that I didn't mention at all is the beta release notes. The notes for 19 are here. When Fx 20 is on beta you can just hack the url to get those notes.

    As you can see, one of the new Desktop features is the built-in PDF reader. This has been riding our trains for almost a year now. We have some documentation about it in this article - View PDF files in Firefox or choose another viewer

    One thing I didn't talk too much about in the video are features that ride the trains for a while. Sometimes we add a feature to Firefox and we don't release it when that version of Firefox moves from Beta to Release. Instead the feature may stay on the Beta train for an extra cycle (or 5). The main way to find out about these feature is the Product coordination meeting. Looking at the notes it seems things often get left out and listening in on the meeting gives you more information. Another place to find out about these features that I didn't mention at all is the beta release notes. [http://www.mozilla.org/en-US/firefox/19.0beta/releasenotes/ The notes for 19 are here.] When Fx 20 is on beta you can just hack the url to get those notes. As you can see, one of the new Desktop features is the built-in PDF reader. This has been riding our trains for almost a year now. We have some documentation about it in this article - [[View PDF files in Firefox without downloading them]]
  3. Here is an approximate list of changes and new features that will be visible to users in Firefox 19 (Desktop & Mobile). Changes and new features are bolded.


    Desktop

      • Reset awesome bar
      • PDF viewer


    Mobile

      • Private Browsing (per tab) landed, but UI will be defaulted off behind a preference
      • Homescreen search widget
      • Improved home page thumbnails
      • Private browsing (per tab)
      • Personas (lightweight themes)
      • Dynamic tile system Nightly (19)
      • Swiping between tabs in awesomescreen
      • Multi-window support on Samsung Note and SIII
      • Allow last tab to be closed

    Mobile

      • Per-tab private browsing - bug 582244
      • Light-weight theming (personas) - bug 783092
    • [[Bug List ]
      • Need visible indicator while a site has camera/microphone access while Firefox window is open
      • Provide a way to open a link into private browsing mode
      • Move the New Private Window menu item under the app button on Windows and Linux if the app button is visible
      • Offer to re-set keyword. URL if it has a non-default value.
      • Download Manager uses global PB service to act on downloads
      • Preference pane options for Firefox Health Report

    Adam

    Here is an approximate list of changes and new features that will be visible to users in Firefox 19 (Desktop & Mobile). Changes and new features are bolded. * [http://www.mozilla.org/en-US/firefox/19.0beta/releasenotes/ [[Firefox Beta - Desktop ]] Desktop ** '''Reset awesome bar''' ** '''PDF viewer ''' * [https://wiki.mozilla.org/Firefox/DeliveryMeetings Firefox/Planning - MozillaWiki ] Mobile ** '''Private Browsing (per tab) landed, but UI will be defaulted off behind a preference''' ** ''' Homescreen search widget''' ** '''Improved home page thumbnails''' ** '''Private browsing (per tab)''' ** '''Personas (lightweight themes)''' ** '''Dynamic tile system Nightly (19)''' ** '''Swiping between tabs in awesomescreen''' ** '''Multi-window support on Samsung Note and SIII''' ** '''Allow last tab to be closed''' * [https://docs.google.com/document/d/1Irb-ZHXPvBhAcnT0HQV150voQN2cJZExsnqTWmqy5us/mobilebasic [[FF19 Feature Review - Google Drive ]] Mobile ** '''Per-tab private browsing - bug 582244''' ** '''Light-weight theming (personas) - bug 783092''' * [https://bugzilla.mozilla.org/buglist.cgi?field0-0-0=flagtypes.name;value0-0-0=ui-review;bug_status=RESOLVED;bug_status=VERIFIED;product=Core;product=Firefox;product=Firefox%20for%20Android;product=Toolkit;chfieldfrom=2012-10-08;resolution=FIXED;chfieldvalue=FIXED;chfieldto=Now;chfield=resolution;type0-0-0=substring;query_format=advanced;list_id=5398345 [[Bug List ]] ** '''Need visible indicator while a site has camera/microphone access while Firefox window is open''' ** '''Provide a way to open a link into private browsing mode ''' ** '''Move the New Private Window menu item under the app button on Windows and Linux if the app button is visible ''' ** '''Offer to re-set keyword. URL if it has a non-default value. ''' ** '''Download Manager uses global PB service to act on downloads ''' ** '''Preference pane options for Firefox Health Report''' Adam

    Modified by adampeebleswrites on

  4. Hi Adam,
    This is a great list. Now let's narrow it down to the things that will be visible in the 19 release. So for example, if the private browsing change is preffed off, we should take it off the list. And bonus points for linking to a source for each change so we can all follow along.
    Thanks,
    Michael

    Hi Adam,<br> This is a great list. Now let's narrow it down to the things that will be visible in the 19 release. So for example, if the private browsing change is preffed off, we should take it off the list. And bonus points for linking to a source for each change so we can all follow along. <br>Thanks,<br> Michael

    Modified by Michael Verdi on

  5. Here is a revised list of changes that I have narrowed down to include only things that will be visible in the 19 release. It's a rough draft with some possible mistakes, so that is why I am keeping my old previous list above, in case I need to re-insert some changes I deleted.


    Desktop

      • Reset awesome bar
      • PDF viewer


    Mobile

      • Homescreen search widget
      • Personas (lightweight themes)
      • Dynamic tile system Nightly (19)
      • Swiping between tabs in awesomescreen
      • Multi-window support on Samsung Note and SIII
      • Allow last tab to be closed

    Mobile '

      • Light-weight theming (personas) - bug 783092
    • [[Bug List ]
      • Provide a way to open a link into private browsing mode
      • Move the New Private Window menu item under the app button on Windows and Linux if the app button is visible


    Adam

    Here is a revised list of changes that I have narrowed down to include only things that will be visible in the 19 release. It's a rough draft with some possible mistakes, so that is why I am keeping my old previous list above, in case I need to re-insert some changes I deleted. * [http://www.mozilla.org/en-US/firefox/19.0beta/releasenotes/ [[Firefox Beta - Desktop ]] Desktop ** '''Reset awesome bar''' ** '''PDF viewer ''' * [https://wiki.mozilla.org/Firefox/DeliveryMeetings Firefox/Planning - MozillaWiki ] Mobile ** ''' Homescreen search widget''' ** '''Personas (lightweight themes)''' ** '''Dynamic tile system Nightly (19)''' ** '''Swiping between tabs in awesomescreen''' ** '''Multi-window support on Samsung Note and SIII''' ** '''Allow last tab to be closed''' * [https://docs.google.com/document/d/1Irb-ZHXPvBhAcnT0HQV150voQN2cJZExsnqTWmqy5us/mobilebasic [[FF19 Feature Review - Google Drive ]] Mobile ' ** '''Light-weight theming (personas) - bug 783092''' * [https://bugzilla.mozilla.org/buglist.cgi?field0-0-0=flagtypes.name;value0-0-0=ui-review;bug_status=RESOLVED;bug_status=VERIFIED;product=Core;product=Firefox;product=Firefox%20for%20Android;product=Toolkit;chfieldfrom=2012-10-08;resolution=FIXED;chfieldvalue=FIXED;chfieldto=Now;chfield=resolution;type0-0-0=substring;query_format=advanced;list_id=5398345 [[Bug List ]] ** '''Provide a way to open a link into private browsing mode ''' ** '''Move the New Private Window menu item under the app button on Windows and Linux if the app button is visible ''' Adam
  6. From Adam's list, here are the changes that are user visible and in Firefox 19 along some links to more info:

    Desktop

    Mobile:

    Note: Many of those mobile changes are listed in the product coordination meeting notes but don't contain links to bugzilla. I found the links by searching bugzilla for those phrases in Firefox for Android bugs that were "fixed". Example: http://people.mozilla.org/~mverdi/screenshots/Search_for_bugs-20130122-115959.jpg

    FYI: I removed these things from Adam's list:

    • Dynamic tile system - this is an "under the hood" change that isn't visible to users
    • Allow last tab to be closed (this is in Fx 20)
    • Provide a way to open a link into private browsing mode - this is part of the per-window private browsing feature that is in Fx 20
    • Move the New Private Window menu item under the app button on Windows and Linux if the app button is visible - this is part of the per-window private browsing feature that is in Fx 20

    Is this everything? Did you find others?

    From Adam's list, here are the changes that are user visible and in Firefox 19 along some links to more info: Desktop *Reset awesome bar search is [https://bugzilla.mozilla.org/show_bug.cgi?id=718088 bug 718088] *PDF viewer is now built-in. Current documentation is - [[View PDF files in Firefox without downloading them]] Mobile:<br> *Homescreen search widget is [https://bugzilla.mozilla.org/show_bug.cgi?id=708707 bug 708707], [http://www.flickr.com/photos/patrykdesign/6477109545/in/photostream mockup] * Mobile themes (Personas) is [https://bugzilla.mozilla.org/show_bug.cgi?id=783092 bug 783092] *Swiping between tabs in awesome screen is [https://bugzilla.mozilla.org/show_bug.cgi?id=759041 bug 759041] *Multi-window support on Samsung Note and SIII is [https://bugzilla.mozilla.org/show_bug.cgi?id=810415 810415] <blockquote>'''Note:''' Many of those mobile changes are listed in the [https://wiki.mozilla.org/Firefox/DeliveryMeetings product coordination meeting notes] but don't contain links to bugzilla. I found the links by searching bugzilla for those phrases in Firefox for Android bugs that were "fixed". Example: http://people.mozilla.org/~mverdi/screenshots/Search_for_bugs-20130122-115959.jpg</blockquote> FYI: I removed these things from Adam's list: *Dynamic tile system - this is an "under the hood" change that isn't visible to users *Allow last tab to be closed (this is in Fx 20) *Provide a way to open a link into private browsing mode - this is part of the per-window private browsing feature that is in Fx 20 *Move the New Private Window menu item under the app button on Windows and Linux if the app button is visible - this is part of the per-window private browsing feature that is in Fx 20 '''Is this everything? Did you find others?'''

    Modified by Michael Verdi on

  7. Desktop

    • ARMv6 expanded support: 600MHz / 512MB / HVGA is Bug 697205

    Mobile

    • Added theme support
    • Support for Traditional Chinese and Simplified Chinese localizations
    Desktop * ARMv6 expanded support: 600MHz / 512MB / HVGA is [[Bug 697205]] Mobile * Added theme support * Support for Traditional Chinese and Simplified Chinese localizations
  8. Can you tell me what webpage or otherwise what method I can use to find out whether a change or feature I thought was going to appear in one version of Firefox (like Firefox 19) is actually going to appear in that version or be pushed back to a later version (like Firefox 20)? I noticed you made the following helpful corrections, which I have listed below. I would like to learn how to correct myself also in the future so I can improve.

    • Dynamic tile system - this is an "under the hood" change that isn't visible to users
    • Allow last tab to be closed (this is in Fx 20)
    • Provide a way to open a link into private browsing mode - this is part of the per-window private browsing feature that is in Fx 20
    • Move the New Private Window menu item under the app button on Windows and Linux if the app button is visible - this is part of the per-window private browsing feature that is in Fx 20

    Thank you, Adam

    Can you tell me what webpage or otherwise what method I can use to find out whether a change or feature I thought was going to appear in one version of Firefox (like Firefox 19) is actually going to appear in that version or be pushed back to a later version (like Firefox 20)? I noticed you made the following helpful corrections, which I have listed below. I would like to learn how to correct myself also in the future so I can improve. * Dynamic tile system - this is an "under the hood" change that isn't visible to users * Allow last tab to be closed (this is in Fx 20) * Provide a way to open a link into private browsing mode - this is part of the per-window private browsing feature that is in Fx 20 * Move the New Private Window menu item under the app button on Windows and Linux if the app button is visible - this is part of the per-window private browsing feature that is in Fx 20 Thank you, Adam

    Modified by adampeebleswrites on

  9. adampeebleswrites said

    Can you tell me what webpage or otherwise what method I can use to find out whether a change or feature I thought was going to appear in one version of Firefox (like Firefox 19) is actually going to appear in that version or be pushed back to a later version (like Firefox 20)?

    Sure. The main place I'm looking is the target milestone of the related bugs http://people.mozilla.org/~mverdi/screenshots/milestone-20130123-091110.jpg

    For example, "Allow last tab to be closed" is bug 811738 which has the target milestone of Firefox 20.

    Sometimes, like in the case of private browsing, it takes more detective work. Mobile is ready but holding off until Firefox 20 so that it ships together with the Desktop feature. That I learned from the coordination meeting.

    ''adampeebleswrites [[#post-50317|said]]'' <blockquote> Can you tell me what webpage or otherwise what method I can use to find out whether a change or feature I thought was going to appear in one version of Firefox (like Firefox 19) is actually going to appear in that version or be pushed back to a later version (like Firefox 20)? </blockquote> Sure. The main place I'm looking is the target milestone of the related bugs http://people.mozilla.org/~mverdi/screenshots/milestone-20130123-091110.jpg For example, "Allow last tab to be closed" is [https://bugzilla.mozilla.org/show_bug.cgi?id=811738 bug 811738] which has the target milestone of Firefox 20. Sometimes, like in the case of private browsing, it takes more detective work. Mobile is ready but holding off until Firefox 20 so that it ships together with the Desktop feature. That I learned from the coordination meeting.
  10. adampeebleswrites said

    Desktop
    • ARMv6 expanded support: 600MHz / 512MB / HVGA is Bug 697205
    Mobile
    • Added theme support
    • Support for Traditional Chinese and Simplified Chinese localizations

    Ok great. "Added theme support" is already on the list but we can add:

    ''adampeebleswrites [[#post-50314|said]]'' <blockquote> Desktop * ARMv6 expanded support: 600MHz / 512MB / HVGA is [[Bug 697205]] Mobile * Added theme support * Support for Traditional Chinese and Simplified Chinese localizations </blockquote> Ok great. "Added theme support" is already on the list but we can add: * ARMv6 expanded support - [https://etherpad.mozilla.org/armv6unblock-FF19 list of additional supported phones] *Support for Traditional Chinese and Simplified Chinese localizations
  11. So there is only one more user visible change in Fx 19. Due to a quirk in the way bugzilla works this slipped past that fancy bugzilla query I linked to at the beginning of this thread. I found this change "simply" by playing around with Firefox 19.

    There is an added menu choice in Facebook Messenger for Firefox that allows you to turn the feature off - screenshot

    So here is our final list of changes:

    Desktop

    Mobile:

    Now let's discuss which of these changes need to be documented (and how) in this workshop thread.

    So there is only one more user visible change in Fx 19. Due to a quirk in the way bugzilla works this slipped past that fancy bugzilla query I linked to at the beginning of this thread. I found this change "simply" by playing around with Firefox 19. There is an added menu choice in [[How does Facebook Messenger for Firefox work?|Facebook Messenger for Firefox]] that allows you to turn the feature off - [http://people.mozilla.org/~mverdi/screenshots/turnoff-20130118-142010.jpg screenshot] ==So here is our final list of changes:== '''Desktop''' *Reset awesome bar search is [https://bugzilla.mozilla.org/show_bug.cgi?id=718088 bug 718088] *PDF viewer is now built-in. Current documentation is - [[View PDF files in Firefox without downloading them]] *Added menu choice in [[How does Facebook Messenger for Firefox work?|Facebook Messenger for Firefox]] that allows you to turn the feature off - [http://people.mozilla.org/~mverdi/screenshots/turnoff-20130118-142010.jpg screenshot] '''Mobile:''' *Homescreen search widget is [https://bugzilla.mozilla.org/show_bug.cgi?id=708707 bug 708707], [http://www.flickr.com/photos/patrykdesign/6477109545/in/photostream mockup] * Mobile themes (Personas) is [https://bugzilla.mozilla.org/show_bug.cgi?id=783092 bug 783092] *Swiping between tabs in awesome screen is [https://bugzilla.mozilla.org/show_bug.cgi?id=759041 bug 759041] *Multi-window support on Samsung Note and SIII is [https://bugzilla.mozilla.org/show_bug.cgi?id=810415 810415] * ARMv6 expanded support - [https://etherpad.mozilla.org/armv6unblock-FF19 list of additional supported phones] *Support for Traditional Chinese and Simplified Chinese localizations '''Now let's discuss which of these changes need to be documented (and how) in [https://support.mozilla.org/en-US/forums/knowledge-base-articles/708918?last=50293 this workshop thread].'''
  12. So I was getting ready to research the following changes/features, " ARMv6 expanded support" and "Support for Traditional Chinese and Simplified Chinese localizations" to see if they would be appearing in Firefox 19, when I tried to first see if I could locate the "Allow last tab to be closed" bug you provided us as an example. But I had some trouble locating it.

    Without knowing that the bug was called 811738, I don't think I would have been able to find it on Bugzilla. I couldn't even find the bug when I searched for the words "Allow last tab to be closed" in Bugzilla. The only record of this bug I could find in the links you gave us at the top of this page was in Firefox coordination meeting . But the bug number, 811738, was not attached to it. So I am curious as to how you found that number.

    My concern is that if I found a change/feature like "Allow last tab to be closed" without a bug number, I am not sure I would be able to find it in Bugzilla and determine whether or not it would appear in Firefox 19. Could you please tell me how I can find a change/feature's bug number or how else I can find out which version of Firefox a change/feature will appear in?

    Thank you

    Verdi said

    adampeebleswrites said
    Can you tell me what webpage or otherwise what method I can use to find out whether a change or feature I thought was going to appear in one version of Firefox (like Firefox 19) is actually going to appear in that version or be pushed back to a later version (like Firefox 20)?

    Sure. The main place I'm looking is the target milestone of the related bugs http://people.mozilla.org/~mverdi/screenshots/milestone-20130123-091110.jpg

    For example, "Allow last tab to be closed" is bug 811738 which has the target milestone of Firefox 20.

    Sometimes, like in the case of private browsing, it takes more detective work. Mobile is ready but holding off until Firefox 20 so that it ships together with the Desktop feature. That I learned from the coordination meeting.

    So I was getting ready to research the following changes/features, " ARMv6 expanded support" and "Support for Traditional Chinese and Simplified Chinese localizations" to see if they would be appearing in Firefox 19, when I tried to first see if I could locate the "Allow last tab to be closed" bug you provided us as an example. But I had some trouble locating it. Without knowing that the bug was called 811738, I don't think I would have been able to find it on Bugzilla. I couldn't even find the bug when I searched for the words "Allow last tab to be closed" in Bugzilla. The only record of this bug I could find in the links you gave us at the top of this page was in [https://wiki.mozilla.org/Firefox/Planning/2012-11-14#Nightly_.2819.29_2 Firefox coordination meeting] . But the bug number, 811738, was not attached to it. So I am curious as to how you found that number. My concern is that if I found a change/feature like "Allow last tab to be closed" without a bug number, I am not sure I would be able to find it in Bugzilla and determine whether or not it would appear in Firefox 19. '''Could you please tell me how I can find a change/feature's bug number or how else I can find out which version of Firefox a change/feature will appear in? ''' Thank you ''Verdi [[#post-50327|said]]'' <blockquote> ''adampeebleswrites [[#post-50317|said]]'' <blockquote> Can you tell me what webpage or otherwise what method I can use to find out whether a change or feature I thought was going to appear in one version of Firefox (like Firefox 19) is actually going to appear in that version or be pushed back to a later version (like Firefox 20)? </blockquote> Sure. The main place I'm looking is the target milestone of the related bugs http://people.mozilla.org/~mverdi/screenshots/milestone-20130123-091110.jpg For example, "Allow last tab to be closed" is [https://bugzilla.mozilla.org/show_bug.cgi?id=811738 bug 811738] which has the target milestone of Firefox 20. Sometimes, like in the case of private browsing, it takes more detective work. Mobile is ready but holding off until Firefox 20 so that it ships together with the Desktop feature. That I learned from the coordination meeting. </blockquote>
  13. adampeebleswrites said

    Without knowing that the bug was called 811738, I don't think I would have been able to find it on Bugzilla. I couldn't even find the bug when I searched for the words "Allow last tab to be closed" in Bugzilla. The only record of this bug I could find in the links you gave us at the top of this page was in Firefox coordination meeting . But the bug number, 811738, was not attached to it. So I am curious as to how you found that number.

    Another good question Adam! I too found this in the meeting notes and then didn't find anything with a simple bugzilla search. So I had to do an advanced search in bugzilla (any of the strings, select product, pick resolution) which found 1327 bugs so I then searched within the page (ctrl+f).

    ''adampeebleswrites [[#post-50416|said]]'' <blockquote> Without knowing that the bug was called 811738, I don't think I would have been able to find it on Bugzilla. I couldn't even find the bug when I searched for the words "Allow last tab to be closed" in Bugzilla. The only record of this bug I could find in the links you gave us at the top of this page was in [https://wiki.mozilla.org/Firefox/Planning/2012-11-14#Nightly_.2819.29_2 Firefox coordination meeting] . But the bug number, 811738, was not attached to it. So I am curious as to how you found that number. </blockquote> Another good question Adam! I too found this in the meeting notes and then didn't find anything with a simple bugzilla search. So I had to do an [http://people.mozilla.org/~mverdi/screenshots/advanced-search-20130128-141333.jpg advanced search in bugzilla ] (any of the strings, select product, pick resolution) which found 1327 bugs so I then [http://people.mozilla.org/~mverdi/screenshots/advanced-search2-20130128-141605.jpg searched within the page] (ctrl+f).
  14. Wow. Good to know for future cases. Thank you Mike.

    Wow. Good to know for future cases. Thank you Mike.
  15. One more thing!

    I didn't make a big deal about this in the video (only mentioned it at the very end) but of course one important step is verifying the changes in the new version of Firefox. So today I found something I hadn't verified and sure enough it is NOT in Firefox 19.

    The Android homescreen search widget (bug 708707) is not available in Firefox 19. In fact, it's not available in any version. So I asked in the #mobile channel on IRC and was directed to bug 833427 which removed it. So we can strike this off our list.

    One more thing! I didn't make a big deal about this in the video (only mentioned it at the very end) but of course one important step is verifying the changes in the new version of Firefox. So today I found something I hadn't verified and sure enough it is NOT in Firefox 19. The Android homescreen search widget ([https://bugzilla.mozilla.org/show_bug.cgi?id=708707 bug 708707]) is not available in Firefox 19. In fact, it's not available in any version. So I asked in the #mobile channel on IRC and was directed to [https://bugzilla.mozilla.org/show_bug.cgi?id=833427 bug 833427] which removed it. So we can strike this off our list.
  16. From FF 19 Beta release notes:

    · Built-in PDF viewer

    · Firefox will offer to reset the Awesomebar search provider, if it has been changed by third-party software or through about:config

    · Canvas elements can export their content as an image blub using canvas.toBlob() (more for developers?)

    From FF 19 1/16/2013 Planning Coordination Meeting

    FF 19 Mobile:

    - Confine cursor positioning thumb control to edit box

    - Text cursor handle doesn't disappear when switching tabs

    - Loading page in background does not update the SurfaceView


    From Mozilla blog – future releases (linked from Planning coordination meeting> link to CNet>blog)

    https://blog.mozilla.org/futurereleases/2013/01/11/firefox-for-android-beta-adds-additional-armv6-support/

    A new Firefox for Android Beta is available for download and testing. This update makes Firefox for Android available to roughly 15 million more phones with additional ARMv6 support. Firefox for Android Beta is now available to phones with minimum requirements of 600MHz, 512MB, HVGA. This includes popular phones like LG Optimus One, T-Mobile myTouch 3G slide, HTC Wildfire S and ZTE R750.

    Firefox for Android Beta includes easy-to-use add-ons that let you change the look of Firefox without getting in the way of your Web experience. You can personalize the look of your Firefox in just a few taps: visit addons.mozilla.org on your Android device, tap the “Personas” tab, select your favorite theme, and then save it to your browser by pressing “Keep it.” New (and old) themes will be automatically saved so you can easily change the look of Firefox any time.

    Firefox for Android Beta also includes Firefox Integration in the Google Search Widget. Now you can launch a Google Search in Firefox for Android Beta, directly from your phone’s homescreen to make it easier and faster to search the Web on your mobile phone. To enable, tap the “Menu” button on your Android device, tap “Add” in the Menu, and then select Firefox under “Widgets.”

    From FF 19 Beta release notes: · Built-in PDF viewer · Firefox will offer to reset the Awesomebar search provider, if it has been changed by third-party software or through about:config · Canvas elements can export their content as an image blub using canvas.toBlob() (more for developers?) From FF 19 1/16/2013 Planning Coordination Meeting FF 19 Mobile: - Confine cursor positioning thumb control to edit box - Text cursor handle doesn't disappear when switching tabs - Loading page in background does not update the SurfaceView From Mozilla blog – future releases (linked from Planning coordination meeting> link to CNet>blog) https://blog.mozilla.org/futurereleases/2013/01/11/firefox-for-android-beta-adds-additional-armv6-support/ A new Firefox for Android Beta is available for download and testing. This update makes Firefox for Android available to roughly 15 million more phones with additional ARMv6 support. Firefox for Android Beta is now available to phones with minimum requirements of 600MHz, 512MB, HVGA. This includes popular phones like LG Optimus One, T-Mobile myTouch 3G slide, HTC Wildfire S and ZTE R750. Firefox for Android Beta includes easy-to-use add-ons that let you change the look of Firefox without getting in the way of your Web experience. You can personalize the look of your Firefox in just a few taps: visit addons.mozilla.org on your Android device, tap the “Personas” tab, select your favorite theme, and then save it to your browser by pressing “Keep it.” New (and old) themes will be automatically saved so you can easily change the look of Firefox any time. Firefox for Android Beta also includes Firefox Integration in the Google Search Widget. Now you can launch a Google Search in Firefox for Android Beta, directly from your phone’s homescreen to make it easier and faster to search the Web on your mobile phone. To enable, tap the “Menu” button on your Android device, tap “Add” in the Menu, and then select Firefox under “Widgets.”
  17. more options

    Hey Michael, I notice that the weekly SUMO meeting videos are posted on that same YouTube channel; is there anything similar for the weekly coordination meetings you mention as a resource in this video? I'd love to be able to listen in each Wednesday but, alas, the day job gets in the way.

    Hey Michael, I notice that the weekly SUMO meeting videos are posted on that same YouTube channel; is there anything similar for the weekly coordination meetings you mention as a resource in this video? I'd love to be able to listen in each Wednesday but, alas, the day job gets in the way.
  18. erinereardon said

    Hey Michael, I notice that the weekly SUMO meeting videos are posted on that same YouTube channel; is there anything similar for the weekly coordination meetings you mention as a resource in this video? I'd love to be able to listen in each Wednesday but, alas, the day job gets in the way.

    Sadly there is not.

    ''erinereardon [[#post-50476|said]]'' <blockquote> Hey Michael, I notice that the weekly SUMO meeting videos are posted on that same YouTube channel; is there anything similar for the weekly coordination meetings you mention as a resource in this video? I'd love to be able to listen in each Wednesday but, alas, the day job gets in the way. </blockquote> Sadly there is not.