#5460: firefox-32.0
-------------------------+--------------------------
 Reporter:  fo           |       Owner:  blfs-book@…
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  7.6
Component:  BOOK         |     Version:  SVN
 Severity:  normal       |  Resolution:
 Keywords:               |
-------------------------+--------------------------

Comment (by ken@…):

 Some things I noticed in the configure file:
 {{{
 --with-mozilla-api-keyfile=file   Use the secret key contained in the
 given keyfile for Mozilla API requests
 --with-google-api-keyfile=file   Use the secret key contained in the given
 keyfile for Google API requests
 --with-bing-api-keyfile=file   Use the client id and secret key contained
 in the given keyfile for Bing API requests
 }}}

  I assume we do not want those.

  Also, there is an option
 {{{
 ac_add_options --enable-default-toolkit=cairo-gtk3
 }}}

 I'm trying that at the moment, my impression is that I will not be using
 it again until a later release: with (apparently) no gtk3 theme set,
 firefox's menus are black and text mostly only appears when the mouse is
 over that line. In particular, this makes my Bookmarks menu very hard to
 navigate, and searches in google have a similar problem (black menu when
 right clicking, e.g. to open in new tab or new window). Also, the trac
 icons below 'Add a comment' have gone, only a row of plain white boxes -
 fortunately the help text is still there when I mouse over them. And I
 think that background colours on the Preview and Submit changes, and on
 the list of tickets, have gone - they all seem to be on a white
 background.

 I _hope_ that is specific to gtk+-3, will have to do another build to find
 out.

-- 
Ticket URL: <http://wiki.linuxfromscratch.org/blfs/ticket/5460#comment:4>
BLFS Trac <http://wiki.linuxfromscratch.org/blfs>
Beyond Linux From Scratch
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-book
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to