Web compatibility interventions firefox что это

Web compatibility interventions firefox что это

Имя: Google
Тип: extension
Версия: 1.1
Включено: true
ID: google@search.mozilla.org

Имя: h264ify
Тип: extension
Версия: 1.1.0
Включено: true
ID: jid1-TSgSxBhncsPBWQ@jetpack

Имя: OZON.ru
Тип: extension
Версия: 1.2
Включено: true
ID: ozonru@search.mozilla.org

Имя: Price.ru
Тип: extension
Версия: 1.0
Включено: true
ID: priceru@search.mozilla.org

Имя: Tampermonkey
Тип: extension
Версия: 4.11.6120
Включено: true
ID: firefox@tampermonkey.net

Имя: uBlock Origin
Тип: extension
Версия: 1.33.2
Включено: true
ID: uBlock0@raymondhill.net

Имя: YouTube High Definition
Тип: extension
Версия: 85.0.0
Включено: true
ID:

Имя: SaveFrom.net помощник
Тип: extension
Версия: 9.31
Включено: false
ID: helper@savefrom.net

Лог ошибок
(#0) Error: WMF VPX video decoding is disabled due to a previous crash.
(#220): GP+[GFX1-]: Present1 failed: 0x887a0001
(#221): GP+[GFX1-]: Present1 failed: 0x887a0001
(#222): GP+[GFX1-]: Present1 failed: 0x887a0001
(#223): GP+[GFX1-]: Present1 failed: 0x887a0001
(#224): GP+[GFX1-]: Present1 failed: 0x887a0001
(#225): GP+[GFX1-]: Present1 failed: 0x887a0001
(#226): GP+[GFX1-]: Present1 failed: 0x887a0001
(#227): GP+[GFX1-]: Present1 failed: 0x887a0001
(#228): GP+[GFX1-]: Present1 failed: 0x887a0001
(#229): GP+[GFX1-]: Present1 failed: 0x887a0001
(#230): GP+[GFX1-]: Present1 failed: 0x887a0001
(#231): GP+[GFX1-]: Present1 failed: 0x887a0001
(#232): GP+[GFX1-]: Present1 failed: 0x887a0001
(#233) Error: WMF VPX video decoding is disabled due to a previous crash.
(#234): CP+[GFX1-]: WMF VPX video decoding is disabled due to a previous crash.

Звуковая подсистема: wasapi
Максимальное число каналов: 2
Предпочтительная частота дискретизации: 44100
Круговая задержка (стандартное отклонение): 24.38ms (0.64)
Устройства вывода
Имя: Группа
Динамики (Realtek High Definition Audio): HDAUDIO\FUNC_01&VEN_10EC&DEV_0269&SUBSYS_10431063&REV_1001\4&29eac456&0&0001
Bluetooth Headset (Bluetooth Audio): BTHENUM\<747413e4-f767-414f-a0c1-6cc1aa9d054c>_LOCALMFG&0000\8&340560cc&0&000000000000_00000000
Bluetooth Headset (2- Bluetooth Audio): BTHENUM\<747413e4-f767-414f-a0c1-6cc1aa9d054c>_LOCALMFG&0000\8&340560cc&1&000000000000_00000000
Bluetooth Headphones (Bluetooth Audio): BTHENUM\<747413e4-f767-414f-a0c1-6cc1aa9d054c>_LOCALMFG&0000\8&340560cc&0&000000000000_00000000
Динамики (USB2.0 Device): USB\VID_1908&PID_2220&MI_01\7&32d8dfd4&0&0001
Разъем внутреннего AUX (2- Bluetooth Audio): BTHENUM\<747413e4-f767-414f-a0c1-6cc1aa9d054c>_LOCALMFG&0000\8&340560cc&1&000000000000_00000000
Realtek Digital Output (Realtek High Definition Audio): HDAUDIO\FUNC_01&VEN_10EC&DEV_0269&SUBSYS_10431063&REV_1001\4&29eac456&0&0001
Разъем внутреннего AUX (Bluetooth Audio): BTHENUM\<747413e4-f767-414f-a0c1-6cc1aa9d054c>_LOCALMFG&0000\8&340560cc&0&000000000000_00000000
Bluetooth Headphones (2- Bluetooth Audio): BTHENUM\<747413e4-f767-414f-a0c1-6cc1aa9d054c>_LOCALMFG&0000\8&340560cc&1&000000000000_00000000
Устройства ввода
Имя: Группа
Микрофон (Microsoft LifeCam VX-1000.): USB\VID_045E&PID_00F7&MI_01\7&22fa9eb5&0&0001
Микрофон (USB2.0 Device): USB\VID_1908&PID_2220&MI_01\7&32d8dfd4&0&0001
Разъем внутреннего AUX (Bluetooth Audio): BTHENUM\<747413e4-f767-414f-a0c1-6cc1aa9d054c>_LOCALMFG&0000\8&340560cc&0&000000000000_00000000
Микрофон (Realtek High Definition Audio): HDAUDIO\FUNC_01&VEN_10EC&DEV_0269&SUBSYS_10431063&REV_1001\4&29eac456&0&0001
Bluetooth Microphone (2- Bluetooth Audio): BTHENUM\<747413e4-f767-414f-a0c1-6cc1aa9d054c>_LOCALMFG&0000\8&340560cc&1&000000000000_00000000
Bluetooth Microphone (Bluetooth Audio): BTHENUM\<747413e4-f767-414f-a0c1-6cc1aa9d054c>_LOCALMFG&0000\8&340560cc&0&000000000000_00000000
Разъем внутреннего AUX (Bluetooth Audio): BTHENUM\<747413e4-f767-414f-a0c1-6cc1aa9d054c>_LOCALMFG&0000\8&340560cc&0&000000000000_00000000
Разъем внутреннего AUX (2- Bluetooth Audio): BTHENUM\<747413e4-f767-414f-a0c1-6cc1aa9d054c>_LOCALMFG&0000\8&340560cc&1&000000000000_00000000
Микрофон (Realtek High Definition Audio): HDAUDIO\FUNC_01&VEN_10EC&DEV_0269&SUBSYS_10431063&REV_1001\4&29eac456&0&0001
Стерео микшер (Realtek High Definition Audio): HDAUDIO\FUNC_01&VEN_10EC&DEV_0269&SUBSYS_10431063&REV_1001\4&29eac456&0&0001

Вывести записи из базы данных

MOZ_CRASHREPORTER_DATA_DIRECTORY: C:\Users\Asus\AppData\Roaming\Mozilla\Firefox\Crash Reports
MOZ_CRASHREPORTER_EVENTS_DIRECTORY: W:\zmk4nlc4.default\crashes\events
MOZ_CRASHREPORTER_PING_DIRECTORY: C:\Users\Asus\AppData\Roaming\Mozilla\Firefox\Pending Pings
MOZ_CRASHREPORTER_RESTART_ARG_0: C:\Program Files\Mozilla Firefox\firefox.exe
MOZ_CRASHREPORTER_STRINGS_OVERRIDE: C:\Program Files\Mozilla Firefox\browser\crashreporter-override.ini

accessibility.force_disabled: 1
accessibility.typeaheadfind.flashBar: 0
browser.cache.disk_cache_ssl: false
browser.cache.disk.enable: false
browser.cache.disk.smart_size.enabled: false
browser.cache.disk.telemetry_report_ID: 42
browser.cache.offline.enable: false
browser.contentblocking.category: strict
browser.download.folderList: 2
browser.search.region: RU
browser.sessionstore.interval: 300000
browser.sessionstore.upgradeBackup.latestBuildID: 20210208133944
browser.startup.homepage: about:blank
browser.startup.homepage_override.buildID: 20210208133944
browser.startup.homepage_override.mstone: 85.0.2
browser.tabs.closeWindowWithLastTab: false
browser.tabs.warnOnClose: false
browser.urlbar.matchBuckets: general:5,suggestion:Infinity
browser.urlbar.oneOffSearches: false
browser.urlbar.placeholderName: Google
browser.urlbar.placeholderName.private: Google
browser.urlbar.searchSuggestionsChoice: true
browser.urlbar.suggest.topsites: false
browser.urlbar.tabToSearch.onboard.interactionsLeft: 2
browser.urlbar.tipShownCount.tabToSearch: 26
browser.urlbar.update1: false
browser.urlbar.update1.interventions: false
browser.urlbar.update1.searchTips: false
browser.urlbar.update1.view.stripHttps: false
browser.urlbar.userMadeSearchSuggestionsChoice: true
doh-rollout.balrog-migration-done: true
doh-rollout.doneFirstRun: true
dom.apps.lastUpdate.buildID: 20161019084923
dom.apps.lastUpdate.mstone: 49.0.2
dom.apps.reset-permissions: true
dom.caches.enabled: false
dom.ipc.plugins.flash.subprocess.crashreporter.enabled: false
dom.ipc.plugins.reportCrashURL: false
dom.ipc.processCount.web: 4
dom.max_script_run_time: 0
dom.mozApps.used: true
dom.push.enabled: false
dom.serviceWorkers.enabled: false
dom.webnotifications.enabled: false
extensions.formautofill.addresses.usage.hasEntry: false
extensions.lastAppVersion: 85.0.2
font.internaluseonly.changed: false
gfx.blacklist.webrender.failureid: FEATURE_FAILURE_DL_BLOCKLIST_NO_ID
gfx.crash-guard.d3d11layers.appVersion: 59.0.2
gfx.crash-guard.d3d11layers.deviceID: 0x0000
gfx.crash-guard.d3d11layers.driverVersion:
gfx.crash-guard.d3d11layers.feature-d2d: false
gfx.crash-guard.d3d11layers.feature-d3d11: false
gfx.crash-guard.d3d9video.appVersion: 53.0.2
gfx.crash-guard.d3d9video.deviceID: 0x0116
gfx.crash-guard.d3d9video.driverVersion: 9.17.10.4229
gfx.crash-guard.glcontext.gfx.driver-init.direct3d11-angle: true
gfx.crash-guard.glcontext.gfx.driver-init.webgl-angle: true
gfx.crash-guard.glcontext.gfx.driver-init.webgl-angle-force-d3d11: false
gfx.crash-guard.glcontext.gfx.driver-init.webgl-angle-force-warp: false
gfx.crash-guard.glcontext.gfx.driver-init.webgl-angle-try-d3d11: true
gfx.crash-guard.status.d3d11layers: 2
gfx.crash-guard.status.d3d9video: 2
gfx.crash-guard.status.glcontext: 2
gfx.crash-guard.status.wmfvpxvideo: 3
gfx.crash-guard.wmfvpxvideo.appVersion: 85.0.2
gfx.crash-guard.wmfvpxvideo.deviceID: 0x0116
gfx.crash-guard.wmfvpxvideo.driverVersion: 9.17.10.4229
gfx.direct3d.last_used_feature_level_idx: 0
gfx.driver-init.appVersion: 42.0
gfx.driver-init.deviceID: 0x0116
gfx.driver-init.driverVersion: 9.17.10.4229
gfx.driver-init.feature-d2d: true
gfx.driver-init.feature-d3d11: true
gfx.driver-init.status: 2
idle.lastDailyNotification: 1613039520
layers.mlgpu.sanity-test-failed: true
media.benchmark.vp9.fps: 83
media.benchmark.vp9.versioncheck: 5
media.gmp-eme-adobe.abi: x86_64-msvc-x64
media.gmp-eme-adobe.enabled: false
media.gmp-eme-adobe.lastUpdate: 1470045120
media.gmp-eme-adobe.version: 17
media.gmp-gmpopenh264.abi: x86_64-msvc-x64
media.gmp-gmpopenh264.autoupdate: false
media.gmp-gmpopenh264.enabled: false
media.gmp-gmpopenh264.lastUpdate: 1592944020
media.gmp-gmpopenh264.version: 1.8.1.1
media.gmp-manager.buildID: 20210208133944
media.gmp-manager.lastCheck: 1612951721
media.gmp-widevinecdm.abi: x86_64-msvc-x64
media.gmp-widevinecdm.autoupdate: false
media.gmp-widevinecdm.enabled: false
media.gmp-widevinecdm.lastUpdate: 1592944021
media.gmp-widevinecdm.version: 4.10.1582.2
media.gmp.storage.version.observed: 1
media.hardware-video-decoding.failed: false
media.navigator.enabled: false
media.peerconnection.enabled: false
media.video_stats.enabled: false
media.videocontrols.picture-in-picture.video-toggle.has-used: true
media.youtube-ua.override.to: 43
network.auth.allow-subresource-auth: 2
network.cookie.prefsMigrated: true
network.dns.disablePrefetch: true
network.http.speculative-parallel-limit: 0
network.predictor.cleaned-up: true
network.predictor.enabled: false
network.prefetch-next: false
network.trr.blocklist_cleanup_done: true
places.database.lastMaintenance: 1613039526
places.history.expiration.transient_current_max_pages: 99999999
plugin.disable_full_page_plugin_for_types: application/pdf
plugin.flash.arch: x86_64-msvc
plugin.flash.blockliststate: 4
plugin.flash.desc: Shockwave Flash 32.0 r0
plugin.flash.lastmod_hi: 367
plugin.flash.lastmod_lo: 272224288
plugin.flash.path: C:\Windows\system32\Macromed\Flash\NPSWF64_32_0_0_303.dll
plugin.flash.version: 32.0.0.303
plugin.importedState: true
plugin.state.npctrl: 0
plugins.ctprollout.cohort: user-changed-from-test
plugins.ctprollout.cohortSample: 0.339308
plugins.flashBlock.enabled: false
privacy.annotate_channels.strict_list.enabled: true
privacy.cpd.offlineApps: true
privacy.cpd.siteSettings: true
privacy.donottrackheader.enabled: true
privacy.purge_trackers.date_in_cookie_database: 0
privacy.purge_trackers.last_purge: 1613039526888
privacy.sanitize.pending: [<"id":"newtab-container","itemsToClear":[],"options":<>>]
privacy.trackingprotection.enabled: true
privacy.trackingprotection.introCount: 20
privacy.trackingprotection.socialtracking.enabled: true
security.disable_button.openCertManager: false
security.enterprise_roots.auto-enabled: true
security.enterprise_roots.enabled: true
security.insecure_field_warning.contextual.enabled: false
security.insecure_password.ui.enabled: false
security.remote_settings.crlite_filters.checked: 1613037616
security.remote_settings.intermediates.checked: 1613037616
security.sandbox.content.tempDirSuffix:
security.sandbox.plugin.tempDirSuffix:
services.sync.declinedEngines: tabs,history,forms,prefs,addons,creditcards
services.sync.engine.addons: false
services.sync.engine.history: false
services.sync.engine.prefs: false
services.sync.engine.prefs.modified: false
services.sync.engine.tabs: false
services.sync.lastPing: 1613036399
services.sync.lastSync: Thu Feb 11 2021 13:57:00 GMT+0300 (Москва, стандартное время)
signon.autologin.proxy: true
signon.importedFromSqlite: true
signon.management.page.hideMobileFooter: true
signon.management.page.sort: last-used
signon.showAutoCompleteOrigins: false
signon.usage.hasEntry: true
signon.usage.lastUsed: 1608025338
storage.vacuum.last.index: 0
storage.vacuum.last.places.sqlite: 1613039521

В папке вашего профиля находится файл user.js, в котором содержатся настройки, созданные пользователем, а не Firefox.

fission.autostart: false
fission.autostart.session: false

Активирована: false
Отключение поддержки доступности: 1
Используемый обработчик Доступности: true
Исполняемый файл поддержки доступности:

NSPR
Ожидаемая минимальная версия: 4.29
Используемая версия: 4.29

NSS
Ожидаемая минимальная версия: 3.60.1
Используемая версия: 3.60.1

NSSSMIME
Ожидаемая минимальная версия: 3.60.1
Используемая версия: 3.60.1

NSSSSL
Ожидаемая минимальная версия: 3.60.1
Используемая версия: 3.60.1

Источник

Webcompat.com Reporter от Thomas Wisniewski

Adds a button to allow users to easily report site compatibility issues at webcompat.com, for the active tab.

Метаданные расширения

Используется

The webcompat.com reporter extension adds a button which allows users to report issues with any site on the web.

Sometimes, sites have bugs or policies that prevent them from working well in every browser. The community at webcompat.com works to help web developers and site owners identify and fix such issues.

If something appears broken, but works in another browser, or if a site or app insists you install another browser this is likely a web compatibility issue that you can report with this add-on.

If you want to report a specific webpage, click on the extension and Firefox will open a new tab to report the issue to webcompat.com. Other than the information in your public report (see below), no other information is collected.

Webcompat.com allows you to report web compatibility issues though a simple webform. Volunteers view the reports, identify solutions, and share the reports and solutions with the website admins. For more details see our About page.

All reports are publicly accessible. Please do not include any confidential or personal information in the content of your report.

The User Agent HTTP header that your browser sends will be recorded in the bug report, if you choose to report a bug, but is hidden by default.

If you choose the anonymous option, the only information that we’ll receive is the content of your report.

Reporting via GitHub

If you choose the GitHub option, webcompat.com will receive your GitHub username and avatar. You can revoke our access to this information at any time from the «Applications» section of your profile page.

If you log into our site using your GitHub user account, webcompat.com will use cookies to record your session information. The cookie will expire when the session ends, i.e., when you click «logout».

Webcompat.com also uses Google Analytics to track usage statistics.

You can find us on Twitter (@webcompat) or on the public mailing list compatibility@lists.mozilla.org (which is archived on Google Groups). These are public forums, so please minimize any personal information you choose to share.

Сообщить о нарушении правил этим дополнением

Если вы считаете, что это дополнение нарушает политики Mozilla в отношении дополнений, или имеет проблемы с безопасностью или приватностью, сообщите об этих проблемах в Mozilla, используя эту форму.

Не используйте эту форму, чтобы сообщать об ошибках или запрашивать новые функции в дополнении; это сообщение будет отправлено в Mozilla, а не разработчику дополнения.

Этому дополнению нужно:

Источник

Compatibility/Interventions Releases

Contents

Currently Released Interventions

A usually up-to-date list of interventions currently shipped can be found with a search for web-bugs issues labeled with «sitepatch-applied», and on Bugzilla with a search for issues with the «[webcompat:sitepatch-applied]» whiteboard tag.

Interventions Release Process

Note: for simplicity, interventions and UA overrides will be referred to solely as interventions in this section.

Intervention Types

There are two types of interventions that we ship in Firefox: high priority and low priority. As a general rule of thumb, a low priority intervention will fix a long-standing bug. A high priority intervention will fix a regression in a top site. In case of confusion, please get in touch with Dennis Schubert for clarification as to which class we’re dealing with.

Low priority interventions should be landed in the Mozilla webcompat-addon repo on GitHub and upstreamed to the relevant tree once per release. These do not require outside collaboration or approval to ship, beyond WebCompat Addon module peer or owner approval.

High priority interventions require shipping out-of-band via Balrog (or Normandy in the future), and as such, require a more in-depth QA and Relman release process.

Shipping Scenarios

All interventions should first land in the Mozilla webcompat-addon repo on GitHub and be accompanied by a version number bump in the addon’s manifest.json. There may be high priority situations where it’s more desirable to land in Mozilla Central first. In these cases, the patches must be backported to GitHub as soon as the intervention is shipped.

Once the intervention is reviewed by a WebCompat Addon module peer and landed, one or more of the following shipping scenarios is followed, depending on the affected platforms and products:

Desktop Releases

Low Priority

High Priority

A current overview of the high-level steps required to ship via ShipIt can be found this Google Doc (Mozilla-internal). Ping :denschub if something needs to be rolled out urgently.

Fenix / Android Components

The system addon is served as a component. Currently Fenix pulls in the latest version, which means the updated addon should be served in the next Google Play Store update.

Firefox iOS

Firefox iOS has currently a very light UA override mechanism (at the time of this writing).

We need to define in cooperation with the Firefox iOS Team on how to remove the pain for users. Most of the issues are identified through webcompat reporting.

Final Checklist when shipping a release

Checklist for follow-ups after landing/deploying everywhere

When the new addon version is released everywhere and there will be no more changes to that version, there are a couple of follow-up steps to do in preparation for the next release cycle.

Interventions Release Rotations

Engineers on the Web Compatibility team will rotate on ownership of shipping new versions of our interventions addons, serving as an Intervention Release Owner (IRO). The process will follow a predictable 4 week schedule, mirroring the proposed 4 week Firefox release schedule, however, we will attempt to land the interventions 1 week before soft freeze (see the schedule above for dates). Another way to look at this is 2 weeks before release.

A tracking bug for the next release should be filed in Bugzilla (in the Web Compatibility::Interventions component). Bugs for adding or removing interventions in the current release cycle should block this bug.

During bug diagnosis, if a site is identified as a low priority intervention candidate, a label is added for the next IRO to take care of during their rotation. Low priority interventions ride the trains without any need for uplifts or out of band shipping mechanisms. The expectation is that there will be a single regular low-priority release for each version of Firefox, driven by the IRO.

High priority interventions should be flagged immediately to the IRO who will then begin the process necessary to ship an off-train intervention.

Interventions Release Rotations

Engineers on the Web Compatibility team will rotate on ownership of shipping new versions of our interventions addons, serving as an Intervention Release Owner (IRO). The process will follow a predictable 4 week schedule, mirroring the proposed 4 week Firefox release schedule.

During bug diagnosis, if a site is identified as a low priority intervention candidate, a label shall be added for the IRO to take care of during their rotation. Low priority interventions ride the trains without any need for uplifts or out of band shipping mechanisms. The expectation is that there will be a single regular low-priority release for each version of Firefox, driven by the IRO.

High priority interventions should be flagged immediately to the IRO who will then begin the process necessary to ship an off-train intervention.

Candidates for interventions

There is a list of sites as well as a Bugzilla bug query for sites that need interventions. In addition, the `type-uaoverride` label may be useful to look at. During a rotation, you should look at both of these sites and determine which are the most important to work on and ship (or close, if appropriate).

Lists of currently deployed interventions across the products and channels are available here https://arewehotfixingthewebyet.com/.

In addition, there is also a `sitepatch-applied` label that helps to keep track of existing interventions. Take care to add this to bugs after shipping a site patch.

IRO Rotation Responsibilities

Intervention Release Owner Schedule

For simplicity, we rotate on a per-release following the Nightly schedule at [Release Calendar].

Источник

Web compatibility interventions firefox что это

I, today, found that Firefox 88.0.1(64bit) sends «/nice%20ports%2C/Tri%6Eity.txt%2ebak» to an website. What is this? Am I infected? The Apache log at the HTTP server is as follows:

The server is located within my home LAN. 192.168.1.188 and xps8940 is the captioned machine that sends this unknown protocol. Tested by Chrome and found no such protocol sent. Could any guru enlighten me? Tak

Выбранное решение

What is the connection with Firefox? Does this happen a certain time after Firefox startup, or when making certain requests?

You could delete the Firefox program folder and reinstall. The program folder usually is

C:\Program Files\Mozilla Firefox

You can download the installer from

Все ответы (4)

Hmm, I assumed that was a random phrase, but actually Google has some matching results:

Seems to be something you could find in your logs if the Nmap utility ran on your network. I don’t think that would come from within Firefox.

When I look at the log more closely, if the last parameter is the host sending the request, the second and third seem to be from the server itself or the return IP address is spoofed:

Hmm, I assumed that was a random phrase, but actually Google has some matching results: https://www.google.com/search?client=firefox-b-1-d&q=%2Fnice%2520ports%252C%2FTri%256Eity.txt%252ebak Seems to be something you could find in your logs if the »’Nmap»’ utility ran on your network. I don’t think that would come from within Firefox. When I look at the log more closely, if the last parameter is the host sending the request, the second and third seem to be from the server itself or the return IP address is spoofed:

Thanks for response, but. IP 192.168.1.188 is not for the server but client, as well as xps8940. This log is taken from the sever, so there is no need to record the server’s IP. Response code 403 is sent out because my httpd.conf setting is to reject the request if no user-agent is specified. So, the server side is safe even if the client is infected.

Выбранное решение

What is the connection with Firefox? Does this happen a certain time after Firefox startup, or when making certain requests?

You could delete the Firefox program folder and reinstall. The program folder usually is

C:\Program Files\Mozilla Firefox

You can download the installer from

Connection is normal http protocol, via LAN cable. It seems happening first thing in the morning after launching FF. Strange is the «GET /», which I never requested. Although (not requested) the response code is 200, and this page did not appear.

I deleted the folder, as you suggested, and re-installed. Rebooted, launched FF, browsed the site, and looked into the log. Alas, the strange access does not exist. Although I could not grab the culprit, I consider the problem resolved. Thanks for your help anyway. Tak

Источник