зеркало из https://github.com/mozilla/gecko-dev.git
Read-only Git mirror of the Mercurial gecko repositories at https://hg.mozilla.org. How to contribute: https://firefox-source-docs.mozilla.org/contributing/contribution_quickref.html
034b23ff41
After this changeset series, the expected flow for web links is: * If not pb, open the Intent URI * If pb and no matching applications, open about:neterror * If pb and one matching application, show this dialog * If pb and > 1 matching application, show the Android system chooser When the user explicitly chooses to share (and thus should infer they're exiting Private Browsing), we don't show the dialog. Custom URIs sort of work: I tested `mailto` and it worked as expected but `tel` does not work as expected (i.e. it doesn't show the dialog). Perhaps there's an explicit "Open dialer" code path. To figure this out, I tested this patch against my Intent URI test page [1]. Decisions around explicitly showing the Android chooser: When there are multiple application matches to an Intent URI, we want to show the Android Intent Chooser. However, we have no way of distinguishing regular tabs from private tabs to the chooser. Thus, if a user chooses "Always" in regular browsing mode, the chooser will not be shown and the URL will be opened. Therefore we explicitly show the chooser (which notably does not have an "Always" option). [1]: https://people.mozilla.org/~mcomella/test/uri.html --HG-- extra : commitid : 1cCVQe5jmNx extra : rebase_source : 146766c2ac5cf8814288377453253debc2ff3f8a |
||
|---|---|---|
| accessible | ||
| addon-sdk | ||
| b2g | ||
| browser | ||
| build | ||
| caps | ||
| chrome | ||
| config | ||
| db/sqlite3 | ||
| devtools | ||
| docshell | ||
| dom | ||
| editor | ||
| embedding | ||
| extensions | ||
| gfx | ||
| hal | ||
| image | ||
| intl | ||
| ipc | ||
| js | ||
| layout | ||
| media | ||
| memory | ||
| mfbt | ||
| mobile | ||
| modules | ||
| mozglue | ||
| netwerk | ||
| nsprpub | ||
| other-licenses | ||
| parser | ||
| probes | ||
| python | ||
| rdf | ||
| security | ||
| services | ||
| startupcache | ||
| storage | ||
| testing | ||
| toolkit | ||
| tools | ||
| uriloader | ||
| view | ||
| webapprt | ||
| widget | ||
| xpcom | ||
| xpfe | ||
| xulrunner | ||
| .clang-format | ||
| .clang-format-ignore | ||
| .eslintrc | ||
| .gdbinit | ||
| .gitignore | ||
| .hgignore | ||
| .hgtags | ||
| .lldbinit | ||
| .ycm_extra_conf.py | ||
| AUTHORS | ||
| Android.mk | ||
| CLOBBER | ||
| GNUmakefile | ||
| LEGAL | ||
| LICENSE | ||
| Makefile.in | ||
| README.txt | ||
| aclocal.m4 | ||
| client.mk | ||
| client.py | ||
| configure.in | ||
| mach | ||
| moz.build | ||
| mozilla-config.h.in | ||
README.txt
An explanation of the Mozilla Source Code Directory Structure and links to
project pages with documentation can be found at:
https://developer.mozilla.org/en/Mozilla_Source_Code_Directory_Structure
For information on how to build Mozilla from the source code, see:
http://developer.mozilla.org/en/docs/Build_Documentation
To have your bug fix / feature added to Mozilla, you should create a patch and
submit it to Bugzilla (https://bugzilla.mozilla.org). Instructions are at:
http://developer.mozilla.org/en/docs/Creating_a_patch
http://developer.mozilla.org/en/docs/Getting_your_patch_in_the_tree
If you have a question about developing Mozilla, and can't find the solution
on http://developer.mozilla.org, you can try asking your question in a
mozilla.* Usenet group, or on IRC at irc.mozilla.org. [The Mozilla news groups
are accessible on Google Groups, or news.mozilla.org with a NNTP reader.]
You can download nightly development builds from the Mozilla FTP server.
Keep in mind that nightly builds, which are used by Mozilla developers for
testing, may be buggy. Firefox nightlies, for example, can be found at:
https://archive.mozilla.org/pub/firefox/nightly/latest-mozilla-central/
- or -
http://nightly.mozilla.org/