Magic-Mirror/gecko-dev
1
0
Fork 0
mirror of https://github.com/mozilla/gecko-dev.git synced 2024-10-21 01:05:45 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
447,244 Commits 615 Branches 98 Tags 5.9 GiB
1509beca39
Commit Graph

18 Commits

Author SHA1 Message Date
Myk Melez
5f5a298ac6 Bug 1135261 - return new window from window.open in desktop runtime; r=marco,smaug,junior,wesj 2015-08-13 19:00:02 -07:00
Junior Hsu
5f5fb8b360 Bug 1043110 - Part 3: test case for widget navigation issue, and a little refactor. r=fabrice 
Refactor detail
1. s/'/"/
2. change the script in |loadFrameScript| to let it have syntax highlight
3. Remove irrelative datastore things

--HG--
extra : rebase_source : 40fbcc96a9d3fc304a7e13298195e29546900fb9
 2015-04-13 15:06:23 +08:00
Carsten "Tomcat" Book
6a7e108e0a Backed out changeset 35c6e7e9c205 (bug 1135261) for test failures in gij in bookmark_edit_test.js on a CLOSED TREE 2015-07-22 08:13:08 +02:00
Myk Melez
9d936dfa4a Bug 1135261 - return new window from window.open in desktop runtime; r=marco,smaug,junior,wesj 2015-07-21 19:15:38 -07:00
Kan-Ru Chen (陳侃如)
b61618c420 Bug 1044736 - Part 6. Widget should only require embed-widgets permission. r=fabrice 
As discussed on dev-webapi[1] the app that wants to use widgets only
need the "embed-widgets" permission to use <iframe mozbrowser mozwidget>

If the app also wants to implement a browser, it could request the
"browser" separately. A <iframe mozbrowser mozwidget> will have
restricted mozbrowser API defined on the prototype if the embedder has
the "brower" permission; they will always throw when used.

[1]: https://groups.google.com/d/msg/mozilla.dev.webapi/uQweGWtVKRA/Bj1jZq3LN-0J

--HG--
rename : dom/apps/tests/test_widget.html => dom/apps/tests/test_widget_browser.html
 2014-11-21 18:56:28 +08:00
Kan-Ru Chen (陳侃如)
be64833b75 Bug 1044736 - Part 5. Extract tests functions to file_test_widget.js. r=fabrice 2014-11-21 18:56:28 +08:00
Wes Kocher
8ea0c6cd56 Backed out changeset 61fc517d0336 (bug 1044736) 2014-11-17 22:44:01 -08:00
Wes Kocher
0e23bb5d7a Backed out changeset b1a6ecfca674 (bug 1044736) 2014-11-17 22:43:57 -08:00
Wes Kocher
2d9f4bd96e Backed out changeset d045286cff6e (original backout of 8 changesets) for not working right a=backout 
--HG--
rename : dom/browser-element/BrowserElementParent.jsm => dom/browser-element/BrowserElementParent.js
 2014-11-17 22:19:49 -08:00
Wes Kocher
3696aa8ceb Backed out 8 changesets (bug 1044736) for breaking the statusbar on b2g a=backout 
Backed out changeset b1a6ecfca674 (bug 1044736)
Backed out changeset 61fc517d0336 (bug 1044736)
Backed out changeset 59a47fafaccf (bug 1044736)
Backed out changeset b3ff4ce20e67 (bug 1044736)
Backed out changeset e4f1f09f150f (bug 1044736)
Backed out changeset 8ecfc1f41ddc (bug 1044736)
Backed out changeset c7c9170ab299 (bug 1044736)
Backed out changeset 78aacc35b4e7 (bug 1044736)

--HG--
rename : dom/browser-element/BrowserElementParent.js => dom/browser-element/BrowserElementParent.jsm
 2014-11-17 20:34:00 -08:00
Kan-Ru Chen (陳侃如)
60c73c4dec Bug 1044736 - Part 6. Widget should only require embed-widgets permission. r=fabrice 
As discussed on dev-webapi[1] the app that wants to use widgets only
need the "embed-widgets" permission to use <iframe mozbrowser mozwidget>

If the app also wants to implement a browser, it could request the
"browser" separately. A <iframe mozbrowser mozwidget> will have
restricted mozbrowser API defined on the prototype if the embedder has
the "brower" permission; they will always throw when used.

[1]: https://groups.google.com/d/msg/mozilla.dev.webapi/uQweGWtVKRA/Bj1jZq3LN-0J

--HG--
rename : dom/apps/tests/test_widget.html => dom/apps/tests/test_widget_browser.html
 2014-11-12 19:27:32 +08:00
Kan-Ru Chen (陳侃如)
532d37e134 Bug 1044736 - Part 5. Extract tests functions to file_test_widget.js. r=fabrice 2014-11-12 19:27:32 +08:00
Carsten "Tomcat" Book
28e9ba1364 Backed out changeset a3604ab2b3ca (bug 1044736) 2014-11-12 08:39:33 +01:00
Carsten "Tomcat" Book
8999b3c663 Backed out changeset 920775ddfb85 (bug 1044736) 2014-11-12 08:39:32 +01:00
Carsten "Tomcat" Book
050c622f95 Backed out changeset 6ccbc46c33db (bug 1044736) 
--HG--
rename : dom/browser-element/BrowserElementParent.jsm => dom/browser-element/BrowserElementParent.js
 2014-11-12 08:39:28 +01:00
Kan-Ru Chen (陳侃如)
4167226bc1 Backed out 8 changesets (bug 1044736) r=bustage 
Backed out changeset 920775ddfb85 (bug 1044736)
Backed out changeset a3604ab2b3ca (bug 1044736)
Backed out changeset fb6a60700803 (bug 1044736)
Backed out changeset 7037d2b40d39 (bug 1044736)
Backed out changeset 1b55f80e1ca6 (bug 1044736)
Backed out changeset f55ff90f2b6f (bug 1044736)
Backed out changeset 8505276285fa (bug 1044736)
Backed out changeset e81aa95ac8d3 (bug 1044736)

--HG--
rename : dom/browser-element/BrowserElementParent.js => dom/browser-element/BrowserElementParent.jsm
 2014-11-12 15:10:27 +08:00
Kan-Ru Chen (陳侃如)
53bbc67989 Bug 1044736 - Part 6. Widget should only require embed-widgets permission. r=fabrice 
As discussed on dev-webapi[1] the app that wants to use widgets only
need the "embed-widgets" permission to use <iframe mozbrowser mozwidget>

If the app also wants to implement a browser, it could request the
"browser" separately. A <iframe mozbrowser mozwidget> will have
restricted mozbrowser API defined on the prototype if the embedder has
the "brower" permission; they will always throw when used.

[1]: https://groups.google.com/d/msg/mozilla.dev.webapi/uQweGWtVKRA/Bj1jZq3LN-0J

--HG--
rename : dom/apps/tests/test_widget.html => dom/apps/tests/test_widget_browser.html
 2014-11-12 14:20:19 +08:00
Kan-Ru Chen (陳侃如)
731f79ef14 Bug 1044736 - Part 5. Extract tests functions to file_test_widget.js. r=fabrice 2014-11-12 14:20:19 +08:00