On 7/26/2012 8:38 PM, Sailfish wrote:
> My bloviated meandering follows what Ron Hunter graced us with on
> 7/26/2012 5:56 PM:
>> On 7/26/2012 5:19 PM, Sailfish wrote:
>>> My bloviated meandering follows what Ron Hunter graced us with on
>>> 7/26/2012 2:32 PM:
>>>> On 7/26/2012 1:04 PM, Sailfish wrote:
>>>>> My bloviated meandering follows what Ron Hunter graced us with on
>>>>> 7/26/2012 10:44 AM:
>>>>>> On 7/26/2012 10:57 AM, WLS wrote:
>>>>>>> On 07/26/2012 11:31 AM, PhillipJones wrote:
>>>>>>>> Ron Hunter wrote:
>>>>>>>>> On 7/26/2012 4:03 AM, Sailfish wrote:
>>>>>>>>>> My bloviated meandering follows what Ron Hunter graced us with on
>>>>>>>>>> 7/26/2012 1:37 AM:
>>>>>>>>>>> On 7/25/2012 3:27 PM, Sailfish wrote:
>>>>>>>>>>>> My bloviated meandering follows what clay graced us with on
>>>>>>>>>>>> 7/25/2012
>>>>>>>>>>>> 9:13 AM:
>>>>>>>>>>>>> On 07/25/2012 12:13 AM, Ron Hunter wrote:
>>>>>>>>>>>>>> On 7/24/2012 8:07 PM, Sailfish wrote:
>>>>>>>>>>>>>>> My bloviated meandering follows what Ron Hunter graced us
>>>>>>>>>>>>>>> with on
>>>>>>>>>>>>>>> 7/24/2012 5:16 PM:
>>>>>>>>>>>>>>>> On 7/24/2012 3:22 PM, Sailfish wrote:
>>>>>>>>>>>>>>>>> REF:
http://hacks.mozilla.org/2012/07/aurora-16-is-out/
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> [excerpt quote="
>>>>>>>>>>>>>>>>> *Other notable changes*
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> o We slightly changed our UA string not to display the 3rd
>>>>>>>>>>>>>>>>> digit
>>>>>>>>>>>>>>>>> of our
>>>>>>>>>>>>>>>>> versioning system.
>>>>>>>>>>>>>>>>> o Incremental GC, a major part in our effort to revamp our
>>>>>>>>>>>>>>>>> Garbage
>>>>>>>>>>>>>>>>> Collector, is now enabled by default.
>>>>>>>>>>>>>>>>> o Opus, a low-latency codec aimed at real-time
>>>>>>>>>>>>>>>>> communication, is
>>>>>>>>>>>>>>>>> enabled
>>>>>>>>>>>>>>>>> by default.
>>>>>>>>>>>>>>>>> o By default, we do not accept anymore MD5 hashes in X.509
>>>>>>>>>>>>>>>>> certificates.
>>>>>>>>>>>>>>>>> o about:memory is now displaying memory usage �per tab�.
>>>>>>>>>>>>>>>>> o We tweaked the context menu, removing the �Send link��
>>>>>>>>>>>>>>>>> item and
>>>>>>>>>>>>>>>>> combining the �Stop� and �Reload� ones.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> See more details in the release notes and in Firefox 16
>>>>>>>>>>>>>>>>> for
>>>>>>>>>>>>>>>>> developers.
>>>>>>>>>>>>>>>>> " /]
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Whoa, boy! That first item is sure to generate a fair
>>>>>>>>>>>>>>>>> amount of
>>>>>>>>>>>>>>>>> caterwauling around the support groups, methinks. :)
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> So, now how can we send a link to someone? Now we have to
>>>>>>>>>>>>>>>> cut and
>>>>>>>>>>>>>>>> paste from the URL to our email client. So much for
>>>>>>>>>>>>>>>> convenience.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> While I haven't loaded Fx16 yet, my interpretation of that
>>>>>>>>>>>>>>> point is
>>>>>>>>>>>>>>> that
>>>>>>>>>>>>>>> it only applies to the context menu. I never use that but,
>>>>>>>>>>>>>>> instead,
>>>>>>>>>>>>>>> using the File submenu for Send link.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Just checked, and while 'email link' is in the file menu,
>>>>>>>>>>>>>> 'send
>>>>>>>>>>>>>> link' is
>>>>>>>>>>>>>> NOT in the context menu. Sigh. Not that I ever used the
>>>>>>>>>>>>>> context
>>>>>>>>>>>>>> menu,
>>>>>>>>>>>>>> but I am sure many people DO.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> The File menu(s) is the *last* place I will go to perform a
>>>>>>>>>>>>> task.
>>>>>>>>>>>>> If there isn't a context or keystroke option...
>>>>>>>>>>>>>
>>>>>>>>>>>>> So, what? The context area getting too full?
>>>>>>>>>>>>> Looking to change something just for the sake of change?
>>>>>>>>>>>>> Context 'Send link' interfering with the normal operation of
>>>>>>>>>>>>> Firefox?
>>>>>>>>>>>>>
>>>>>>>>>>>>> There is no way I can look at this decision as an improvement.
>>>>>>>>>>>>>
>>>>>>>>>>>>> I _can_ imagine the Moz devs slapping each other on the back,
>>>>>>>>>>>>> celebrating the implementation of this 'feature', after
>>>>>>>>>>>>> weeks of
>>>>>>>>>>>>> careful deliberation.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Reminiscent of the recent discussion in the dev group about
>>>>>>>>>>>>> renaming
>>>>>>>>>>>>> newly opened, blank tabs, something other than 'New Tab'.
>>>>>>>>>>>>>
>>>>>>>>>>>>> I really do admire the enormous time and effort the devs put
>>>>>>>>>>>>> into
>>>>>>>>>>>>> resolving these critical, showstopping bugs.
>>>>>>>>>>>>
>>>>>>>>>>>> This is really a trivial context-menu item to re-enact. If
>>>>>>>>>>>> there's a
>>>>>>>>>>>> need, I'm certain someone will add it back in form of an
>>>>>>>>>>>> add-on.
>>>>>>>>>>>> Here's
>>>>>>>>>>>> the actual XUL entry that was removed from
>>>>>>>>>>>> chrome://browser/content/browser.xul:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> <menuitem id="context-sendlink"
>>>>>>>>>>>> label="&sendLinkCmd.label;"
>>>>>>>>>>>> accesskey="&sendLinkCmd.accesskey;"
>>>>>>>>>>>> oncommand="gContextMenu.sendLink();"/>
>>>>>>>>>>>>
>>>>>>>>>>>> Myself, I'm all for cleaning up seldom used old cruft, er,
>>>>>>>>>>>> stuff
>>>>>>>>>>>>
>>>>>>>>>>> Seldom used? By whom? Me, yep, you, apparently, but a testpilot
>>>>>>>>>>> run
>>>>>>>>>>> on it would have been wise before removing it.
>>>>>>>>>>>
>>>>>>>>>> My understanding of Test Pilot is that it is used to study new
>>>>>>>>>> prototype
>>>>>>>>>> ideas. I believe they already have in place the mechanism to
>>>>>>>>>> record
>>>>>>>>>> various UI usage stats. Not every UI change deserves a formal
>>>>>>>>>> study
>>>>>>>>>> before deciding to change it.
>>>>>>>>>>
>>>>>>>>> Ahhh, but just because no on on the developer panel uses a
>>>>>>>>> function,
>>>>>>>>> context menu, or key combination, doesn't mean many, or even MOST
>>>>>>>>> users
>>>>>>>>> don't, and test pilot DOES provide that information.
>>>>>>>>> If you run it through test pilot, at least you discover that
>>>>>>>>> actual
>>>>>>>>> usage. Look at all the effort that went into the tab grouping
>>>>>>>>> development, to please less than 3% of users (according to test
>>>>>>>>> pilot).
>>>>>>>>> They put the thing in there to get this kind of information, so
>>>>>>>>> they
>>>>>>>>> should use it.
>>>>>>>>>
>>>>>>>> Probably end up like feedback thing they in SM and Ff for years.
>>>>>>>> turned
>>>>>>>> out they removed it because developers refused to look at it
>>>>>>>> from day
>>>>>>>> one. So it was removed. All the reports from it were going in bit
>>>>>>>> bucket by design. It was just put in to placate users, making them
>>>>>>>> think they were contributing something.
>>>>>>>>
>>>>>>>
>>>>>>> Huh?
>>>>>>>
>>>>>>> My Firefox 17.0 Nightly still has Submit Feedback under Help, and
>>>>>>> they
>>>>>>> do read it. Here is one from this weeks meeting notes.
>>>>>>>
>>>>>>>
http://blog.mozilla.org/meeting-notes/archives/1023
>>>>>>>
>>>>>>> "Favicon
>>>>>>>
>>>>>>> The removal of Favicons from the awesome bar is receiving generally
>>>>>>> negative feedback [12]. It is difficult to be precise since the
>>>>>>> descriptions can vary greatly. Might need to do more focused
>>>>>>> research."
>>>>>>>
>>>>>>> [12]
http://tinyurl.com/codplzg
>>>>>>>
>>>>>>> Believe what you want.
>>>>>>>
>>>>>> My response to removing the favicon was decidedly negative, but they
>>>>>> didn't ask me, nor do they, apparently, care.
>>>>>>
>>>>> I like the new method over a favicon advert. Now, the URLbar icon
>>>>> actually conveys something useful in terms of a site's identity. I'm
>>>>> glad they didn't waste time going out with a survey on this since most
>>>>> set-in-their-ways users would have voted for the previous favicon
>>>>> display.
>>>>>
>>>> I can recognize the favicon for my usual sites, and the URL is RIGHT
>>>> THERE, for those who like text. I use the favicons on the bookmarks
>>>> toolbar so I can get a LOT of sites on my toolbar. The justification
>>>> was that some sites were sending favicons that looked like 'lock
>>>> icons', and misleading users as to the security of the site. A valid
>>>> issue, but simply moving the secure site icon back where it was eons
>>>> ago, and sites couldn't influence, would have made better sense, at
>>>> least to me.
>>>>
>>> Ergonomically, I disagree. The old way required that I move my eyes from
>>> the URLbar down to the status bar to determine if the lock was engaged.
>>> Now, it's right there with the URL. Much better, no?
>>>
>>> Also, the favicons are still there in the bookmarks list and on their
>>> respective tabs.
>>>
>> You assume that everyone USES tabs. Some of us don't use tabs for
>> days at a time. About the only time I actually have more than one tab
>> active is when I am using the add-ons tab, so I don't keep the tab bar
>> visible all the time. Ergo, no favicon. Again, everyone uses the
>> program differently.
>>
> That's a fairly remote edge case there. Anyway, what's the need of a
> favicon if you only have one site open?
>
What's the need of it on a tab, if you rarely have more than 3 tabs open?