IOL Technique
So with the changes coming next month, does that kill the IOL technique?
I've noticed a lot of threads about it are gone now. ------------------------------ Jeff Peterson ----------...
Forum Discussion
Hi Jeff,
Quickbase has been making changes to how we handle JavaScript and other content being inserted into the platform outside of code pages (where it is supported and will be even after these changes). Starting in April we have been working to close 3 separate loopholes that were used to insert JavaScript where it was unsupported starting with Rich Text manual entry fields, then app and realm branding, and finally in our upcoming August release next month we will be closing the last area which is formula fields.
------------------------------
Evan Martinez
Community Marketing Manager
Quickbase
------------------------------
Quickbase has been making changes to how we handle JavaScript and other content being inserted into the platform outside of code pages (where it is supported and will be even after these changes). Starting in April we have been working to close 3 separate loopholes that were used to insert JavaScript where it was unsupported starting with Rich Text manual entry fields, then app and realm branding, and finally in our upcoming August release next month we will be closing the last area which is formula fields.
With this upcoming release, builders will no longer be able to save changes to any formula rich text fields that contain unsupported content such as JavaScript. Instead, builders will see an error message warning them that unsupported content has been detected and changes will not save. This will not remove existing JavaScript but will prevent any further edits or changes to what is in the field. Builders will only be able to save changes to these fields after our August Release (tentatively scheduled for 08-15-2021) after they have removed any unsupported content.
With this series of changes, we will not intentionally disable any existing solutions that leverage inserted JavaScript. However, it is impossible for us to test inserted JavaScript as we make changes to the Quickbase platform. A routine upgrade to an open-source library, a change to styling, or a change to our document object model (DOM) may cause these custom solutions to break without warning. This has always been a risk of using such unsupported techniques. However, as we progress with projects like modernizing our interface in 2021 and beyond, these kinds of changes will become more frequent. And if a solution stops working for one of these reasons after the area has been closed, app builders will not be able to edit the JavaScript to fix it. What this means is that techniques like IOL you have in place are not being intentionally broken but going forward from the release new IOL will not be possible and any places where it is today will be able to be removed and replaced with supported features but won't be able to be changed. You can learn more about our full plan, the reason these changes are important, and the earlier loopholes we have closed in our blog post here.
------------------------------
Evan Martinez
Community Marketing Manager
Quickbase
------------------------------
Will service workers be impacted by these changs?
- I think the only thing they could really do is prevent you from using JavaScript to trigger them in code pages but then code pages would be pretty useless. At this time doing it in a code page is even in line with what Quickbase wants, they only want JavaScript ran in there. So I see it as following their rules and still getting to have your JavaScript usage in the apps.
- Hi G,
These changes do not change service workers as that functionality lives in your browsers. Service workers in your browser are changing the information delivered by Quickbase on your end very much like how an Ad Blocker works by finding the ads in a page after it has been delivered and extracting them. Service Workers is not something we recommend or support though in a similar vein to JavaScript inserted outside of code pages.
Since it changes things via your browser its use opens up concerns around your security and displaying your data with integrity. Beyond that because it is a browser add on that looks for things within the pages being delivered and executes changes it is vulnerable to breaking or causing strange behaviors when we update or change elements in Quickbase since we can't and don't test for these add ons. A great example would be a Service Worker today that alters your old table reports could break or cause a strange display in new table reports that might go unnoticed by your users for a time. Between the security concerns and the possibility of change we don't recommend them but this program isn't changing them since they happen on the browser side.
------------------------------
Evan Martinez
Community Marketing Manager
Quickbase
------------------------------
