Bug 151856
| Summary: | There is no way to detect that content blocker contains errors in Safari OS X | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Andrey Meshkov <am> |
| Component: | WebKit Misc. | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | achristensen, benjamin |
| Priority: | P2 | ||
| Version: | WebKit Nightly Build | ||
| Hardware: | Mac | ||
| OS: | Unspecified | ||
Andrey Meshkov
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.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Andrey Meshkov
It is now possible to detect errors.