Search results
Page title matches
- #REDIRECT [[Sumo/Unofficial FF 60 Support Report]]50 bytes (6 words) - 04:25, 9 May 2018
-
834 bytes (110 words) - 17:09, 16 May 2018
- = UNOFFICIAL SUMO FF 60 Support Report = ...uk8CjY_eDwK6I/edit#gid=1589581957 Spreadsheet of bugs being considered for FF 60.0.1]2 KB (310 words) - 03:05, 9 June 2018
-
7 KB (981 words) - 16:27, 8 August 2018
-
2 KB (325 words) - 16:32, 8 August 2018
-
1 KB (133 words) - 14:10, 11 September 2018
-
4 KB (474 words) - 06:02, 16 October 2018
- [[Category:L10n Teams|ff]] ===Fulah / Pulaar-Fulfulde (ff)===2 KB (342 words) - 05:36, 31 August 2019
Page text matches
- * test native app support is on by default. Toggle switch. (Settings > FF Home) ...is the default app to be launched for websites. Toggle switch.(settings > FF Home)11 KB (1,689 words) - 15:46, 4 November 2010
- *Have never tested in FF Mobile (sorry!). ...ss to firebug and other dev tools. Knowing that having things work in both FF environments would be fantastic.51 KB (8,234 words) - 18:50, 19 July 2012
- |class="header"|FF or Platform? |Ff19 KB (2,658 words) - 14:25, 30 June 2009
- ...i-view_forum_thread.php?forumId=1&comments_parentId=371191] | font-face in FF 3.5 not so pretty ...umId=1&comments_parentId=372185] | Netflix's steaming movies jerky only in FF 3.573 KB (9,768 words) - 09:31, 14 July 2021
- ...ne). The syntax should be about the same, so something like <!--[if lte FF 6]> <![endif]--> would be appropriate. ...for working results would be nice. If a link returns a "not found" or so, FF could darken that link (or alter an tiny image in front of the link - sad s70 KB (11,938 words) - 18:34, 2 December 2009
- ...ser/themes && make -s -j8 -C obj-ff-dbg/browser/base && make -s -j8 -C obj-ff-dbg/browser/app obj-ff-dbg/dist/MinefieldDebug.app/Contents/MacOS/firefox-bin -no-remote -P tcc19 KB (3,010 words) - 17:26, 15 March 2011
- ** FF b4 code freeze, fuzzy text solved: we should plan for 1.6b1 soon ** set true by default, false for linux on FF 3.64 KB (592 words) - 17:54, 17 August 2010
- ** FF b4 code freeze, fuzzy text solved: we should plan for 1.6b1 soon ** DONE set true by default, false for linux on FF 3.65 KB (668 words) - 17:44, 24 August 2010
- '''Platforms:'''MACOSX: FF 3.6.13<br> '''Platforms:'''Ubuntu: FF 3.6.13<br>4 KB (563 words) - 07:32, 22 January 2011
- *Allow "triggers" to be set 1) before FF attempts to start downloading a page, 2) when the page has been downloaded ...pty tab. I suggest that when a URL is attempted to be opened in a new tab, FF displays the URL in the tab, but shows it "grayed out" (but still selectabl87 KB (15,483 words) - 11:18, 30 June 2011
- ** panel tab button ui style problem on FF 4.0 == JaegerMonkey (FF 4.1?) ==4 KB (618 words) - 18:01, 31 August 2010
- ** DONE panel tab button ui style problem on FF 4.0 == 1.6 on FF 4.0 ==5 KB (662 words) - 17:02, 14 September 2010
- == 1.6 on FF 4.0 == * FF 4.0b7 status?5 KB (735 words) - 18:14, 28 September 2010
- == 1.6 on FF 4.0 == * FF 4.0b7 status?6 KB (833 words) - 17:02, 12 October 2010
- == 1.6 on FF 4.0 == * FF 4.0b7 status?6 KB (835 words) - 17:01, 12 October 2010
- == 1.6 FF 4.0 == * FF 4.0, still in limbo1 KB (180 words) - 19:03, 23 November 2010
- ===FF 10=== ===FF 11===2 KB (281 words) - 22:53, 31 January 2012
- ===FF 10=== ===FF 11===3 KB (475 words) - 23:31, 16 February 2012
- ===FF 10=== ===FF 11===2 KB (288 words) - 22:53, 7 February 2012
- ===FF 10=== ===FF 11===3 KB (391 words) - 18:49, 17 February 2012