![]() ![]() Therefore Apple intentionally(!) removed the ability to change the font size within the modern web engine on iPads (but not on iPhones, because these are still treated as "Mobile“ devices). And Apple thinks that the ability for a web site to change the font size does not match this „Desktop“ statement. The „problem“ with the modern web engine since iOS 13 is that Apple decided that the iPad should be marketed as a device with „Desktop computer feeling“ which could replace a notebook computer etc. User Interface Changing the font size no longer works on the iPad. The old filters could only block based on the URL of a resource, the new filters can be much more detailed, for example a filter can differentiate between first-party and third-party resources and between different file types and even limit a filter to certain domains of the main document. The filter of iCab Mobile 10 itself provides much more paramaters than the filters of iCab Mobile 9. This is useful because iCab Mobile 10 supports much more features of these third-party filters than iCab Mobile 9 and older.Īll the filters you've created yourself should be checked manually after updating from iCab Mobile 9 to 10, to make sure that there are no unwanted issues (like the exception filters which won't work anymore). So when updating from iCab Mobile 9 or older to iCab Mobile 10 and newer, you should delete the old "whitelist" filter collection (the ones for the exception filters), because it would no longer work.Īlso all the third-party filters (AdBlock Plus, Easylist, uBlock and compatible) which you've imported in the past in iCab Mobiel 9 and older should be deleted in iCab Mobile 10 and newer and imported again. ![]() ![]() Here the exception filters must be located within the same collection in which those filters are located which should be overridden by the exception filter. This doesn't work in the new filter system anymore. ![]() In the old filter system it was common to have a dedicated collection which comatins the exception filters and which was placed before all other collections. This is important for the exception filters. This is an important difference (iCab Mobile 10 will automatically change the order when converting the old filters into the new ones after updating the App).Īlso in the old filter system filters of one collection can affect filters of other collections (important for the exception filters), the new filter system keeps each collection separate, so filters in different collections do not have influence of filters in other collections. The new filter system expects the exception filters after the filters they should override. But the old filter system expects the exception filters located before the other filters they would override. In general the filters are searched in the given order. Individual filters can block certain resources, hide page elements (CSS-based filters), block cookies (only supported by iCab Mobile 10 and later) and define exception filters which can override other filters to make sure that in this special case the resource is not blocked but loaded. This is the same for the old and the new filter system. Filters How do the filters work in iCab Mobile 10 and later, what are the differences between the filters of iCab Mobile 9.x and older and the ones of iCab Mobile 10 and newer?įilters are organized in "collections", filters within a collection belong together, for example because they have the same purpose (like blocking Ads). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |