-
Notifications
You must be signed in to change notification settings - Fork 439
Move µBlock.transposeType()
to Chromium's platform-specific code
#536
Comments
µBlock.transposeType
to Chromium's platform-specific code µBlock.transposeType()
to Chromium's platform-specific code
Would it be possible to also not limit the types to Chromium's list. Firefox can differentiate many more types, and being able to see the exact type (especially these: OBJECT_SUBREQUEST, FONT, MEDIA, BEACON) instead of |
Yes, it's possible but this will require careful revision of entry points to be sure that wherever a specific set of types is expected that it redirects the type to [add more as we identify these places] Edit: Also, I wished I had normalized to type names which are less specific to Chromium, so maybe an opportunity to do that at the same time, i.e. |
I notice that with Firefox, the hostname information is readily available: |
How is this related to this issue? |
I want to take care of this at the same time, working to normalize |
Aha. In that case, it actually has an |
This code needs to be platform-specific. For examples, some platforms may be able to identify font objects and thus there is no need to try to guess fonts in the platform-independent code. Also, the workaround Chromium bug to transpose
image
,stylesheet
orother
should not be applied to other platform not suffering the bug.The text was updated successfully, but these errors were encountered: