Bug 151856 - There is no way to detect that content blocker contains errors in Safari OS X
Summary: There is no way to detect that content blocker contains errors in Safari OS X
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit Misc. (show other bugs)
Version: WebKit Nightly Build
Hardware: Mac Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-04 03:42 PST by Andrey Meshkov
Modified: 2020-01-29 02:10 PST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrey Meshkov 2015-12-04 03:42:30 PST
Hi!

The problem is with Safari method "safari.extension.setContentBlocker".

On iOS we at least can get content blocker compilation status in a callback.
But on OS X the only way to check that something is wrong is to inspect system.log.
Comment 1 Andrey Meshkov 2020-01-29 02:10:07 PST
It is now possible to detect errors.