This forum is a discussion about improving the "How to stop Firefox from automatically making connections without my permission" article. If you'd like to participate, please register.

If you need help with Firefox, please ask a question.

Add fetching of search plug-in icons

  • 3 Replies
  • Last reply by Joni
  1. Marcus320 0 posts
    Report Abuse

    Please add following point to the list:

    Fetching of search plug-in icons

    Search plug-in icons are fetched if provided as "http: URI". That is done once per search plug-in, upon which Firefox caches its icon by replacing the "http: URI" with a "data: URI" containing the base64 encoded icon.

    This is of importance e.g. to Firefox on LiveCD distributions using "http: URI" for search plug-in icons, resulting in fetching of the icons on each LiveCD session.

    Providing search plug-in icons as "data: URI" from the beginning (e.g. by letting Firefox fetch the icon from "http: URI" and then using the resulting "data: URI" on the LiveCD) will disable this feature.

    See https://developer.mozilla.org/en-US/docs/Creating_OpenSearch_plugins_for_Firefox for details on search plug-in creation.

    Please add following point to the list: '''Fetching of search plug-in icons''' Search plug-in icons are fetched if provided as "http: URI". That is done once per search plug-in, upon which Firefox caches its icon by replacing the "http: URI" with a "data: URI" containing the base64 encoded icon. This is of importance e.g. to Firefox on LiveCD distributions using "http: URI" for search plug-in icons, resulting in fetching of the icons on each LiveCD session. Providing search plug-in icons as "data: URI" from the beginning (e.g. by letting Firefox fetch the icon from "http: URI" and then using the resulting "data: URI" on the LiveCD) will disable this feature. See https://developer.mozilla.org/en-US/docs/Creating_OpenSearch_plugins_for_Firefox for details on search plug-in creation.
  2. AliceWyman 4163 posts
    Report Abuse

    This got overlooked. I'll add it to the Need changes list for review.

    This got overlooked. I'll add it to the Need changes list for review.
  3. philipp 557 posts
    Report Abuse

    this doesn't appear to affect any search plugins built-in by default (at least the ones that i got to inspect) - so should this go into the user content section?

    this doesn't appear to affect any search plugins built-in by default (at least the ones that i got to inspect) - so should this go into the user content section?
  4. Joni 171 posts
    Report Abuse

    Thanks for bringing this up. Philipp, I do think this should go in user-invoked content.

    Thanks for bringing this up. Philipp, I do think this should go in user-invoked content.