Re: What are your use cases for the Touch Bar on the new MacBook Pro?

[Haik Aftandilian]

What about using it to help detect phishing sites.

For example, when filling out a user/password form, if the touch bar
displayed the domain name (not the full URL) we're submitting to (for
example mybank.com), that might help prevent some phishing attacks. The
user just has to glance down at the bar to confirm they're submitting to
mybank.com.

This only works if we don't allow web pages to control what is displayed on
the touch bar.

On Tue, Jan 3, 2017 at 9:17 AM, Stephen A Pohl  wrote:

> We are gathering ideas for possible use cases of the Touch Bar on the
> new MacBookPro and would like to hear from you! What would improve your
> workflow? What would help our users?
>
> We will develop[1] a solid 1.0 API around the top features to get the
> ball rolling and will iterate on these going forward.
>
> Apple has outlined guidelines and best practices[1] for the Touch Bar
> that are good to keep in mind. Here are some of the most important
> points to consider:
> 1. Design a contextual experience. Make the Touch Bar relevant to the
> current context on the main screen.
> 2. Use the Touch Bar as an extension of the keyboard and trackpad, not
> as a display.
> 3. **Don’t expose functionality solely in the Touch Bar.
> 4. Avoid using the Touch Bar for tasks associated with well-known
> keyboard shortcuts.
>
> -Stephen
>
> [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1313455
> [2]
> https://developer.apple.com/library/content/documentation/
> UserExperience/Conceptual/OSXHIGuidelines/AbouttheTouchBar.html#//apple_
> ref/doc/uid/2957-CH104-SW1
> ___
> 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: Please don't abuse "No bug" in commit messages

[Steve Fink]

On 02/06/2017 08:19 AM, Mike Hoye wrote:



On 2017-02-03 2:01 PM, Steve Fink wrote:
Typo/whitespace - No bug is fine, but if it is associated with a 
recent landing of some bug, then you should use that bug number 
anyway. Makes uplifts cleaner.


Whitespace errors seem like a wierd thing for an engineer to be 
working on?. Code cleanup bugs are how a lot of people get started, 
and could also have automatic formatting. Employees pushing whitespace 
around seems like a distant third-best.


While I also don't want people to suffer from unnecessary process 
overhead, I also want small-change bugs to be discoverable by people 
trying to start contributing. I'm not sure where that line is, but 
changes without bugs means nobody else could have helped make those 
changes. 


The scenario I'm thinking of is that I land something, and notice (or 
somebody points out) that I added whitespace at the end of a line 
somewhere. Landing an immediate fix seems like the lowest overhead way 
of dealing with it, other than ignoring it entirely. But ignoring it 
would cause a small amount of friction for other people, so I'd rather 
clean up after myself if I notice.


A related situation is when starting to work on something, you find it 
has trailing whitespace scattered around. I like to have a separate 
whitespace fixup commit, to make the following changes more clear. 
That's the case where I wouldn't look up the bug where the whitespace 
was landed. (First, because it's a bit of nuisance to look up, and 
second, associating it with some old bug is going to cause more harm 
than good, especially if things have modified stuff in between.) I'm not 
really sure whether it's better to label such a changeset with "No bug" 
or with the new bug from the following changeset. I guess the latter 
would be better for uplifts. (Though I'll often squash things that I may 
want to uplift and attach that as an upliftable patch so I don't have to 
request approval on multiple patches and it's just easier to deal with 
one patch at a time.)


Otherwise, yeah, I'm not going to go around looking for whitespace 
problems. I only deal with whitespace if it gets in my way, or if I 
recently introduced it.


___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

[Firefox Desktop] Issues found: January 30th to February 3rd

[Cornel Ionce]

Hi everyone,

Here's the list of new issues found and filed by the Desktop Release QA 
Team last week, *January 30  - February 03* (week 5).


Additional details on the team's priorities last week, as well as the 
plans for the current week are available at:


   https://public.etherpad-mozilla.org/p/DesktopManualQAWeeklyStatus



*RELEASE CHANNEL*
none

*BETA CHANNEL*
ID  Summary Product Component   Is a regression 
Assigned to
1335088 
Grid highlighter tool not working after exiting Offline Mod
Firefox
Developer Tools: Inspector
NO  Matteo Ferretti 
1336439 
[FirstPartyIsolation] MSN articles can't be shared via Facebook
Core
DOM: Security
NO  NOBODY
1336440 
	[FirstPartyIsolation] Ebay-kleinanzeigen.de items can't be shared via 
Facebook

CoreDOM: Security   NO  NOBODY
1336441 
[FirstPartyIsolation] Sabq.org items can't be shared via Facebook
CoreDOM: Security   NO  NOBODY
1336442  	[FirstPartyIsolation] Onedio.com 
items can't be shared via Facebook

CoreDOM: Security   NO  NOBODY
1336458  	[FirstPartyIsolation] Unable to 
login using Facebook on As.com

CoreDOM: Security   NO  NOBODY
1336460  	[FirstPartyIsolation] Unable to 
login using Facebook on Twitch.tv

CoreDOM: Security   NO  NOBODY
1336461 
[FirstPartyIsolation] Unable to login using Facebook on Adf.ly
CoreDOM: Security   NO  NOBODY
1336462 
[FirstPartyIsolation] Unable to login using Facebook on Wikia.com
CoreDOM: Security   NO  NOBODY
1336463 
[FirstPartyIsolation] Unable to login using Facebook on Espn.com
CoreDOM: Security   NO  NOBODY
1336464 
[FirstPartyIsolation] Unable to login using Facebook on Dailymotion.com
CoreDOM: Security   NO  NOBODY
1336465 
[FirstPartyIsolation] Unable to login using Facebook on Sabah.com.tr
CoreDOM: Security   NO  NOBODY
1336466
 
[FirstPartyIsolation] Facebook pop-up does not close after entering 
credentials on Cdiscount.com 	Core 	DOM: Security 	NO 	NOBODY



*AURORA CHANNEL*
none

*NIGHTLY CHANNEL
*
ID  Summary Product Component   Is a regression 
Assigned to
1335360 
Highlighted word has no space after stylized characters Toolkit
Find Toolbar
	YES 
 
	NOBODY

1336066 
	No screen' shows preview after clicking once on the device permission 
in the location bar

Firefox
Device Permissions
YES NOBODY



*ESR CHANNEL*
none


Regards,
Cornel Ionce
Team Lead
SOFTVISION

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: Please don't abuse "No bug" in commit messages

[Mike Hoye]

On 2017-02-03 2:01 PM, Steve Fink wrote:
Typo/whitespace - No bug is fine, but if it is associated with a 
recent landing of some bug, then you should use that bug number 
anyway. Makes uplifts cleaner.


Whitespace errors seem like a wierd thing for an engineer to be working 
on?. Code cleanup bugs are how a lot of people get started, and could 
also have automatic formatting. Employees pushing whitespace around 
seems like a distant third-best.


While I also don't want people to suffer from unnecessary process 
overhead, I also want small-change bugs to be discoverable by people 
trying to start contributing. I'm not sure where that line is, but 
changes without bugs means nobody else could have helped make those changes.


- mhoye
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform