Blog Post
@Sharon Faust I'm glad they have been helpful to your questions
1. You will be able to still call the QB styles for buttons with the caveat that if we update or change the styles they would update for you. Bootstrap styles like the one here should also be just fine.
2. Iframes embedded on forms have been identified as one of the serious possible concerns so that is at the heart of them being locked down in this update. The product team is laser focused though on delivering a safe way to allow for embedding and there is already a working model of that in our new dashboards to allow a secure iframe.
@Adam Keever I see you are chatting with Ryan over on the community slack, he is probably best equipped to help you dig into the specifics of how you might do that one and get into all the requirements you would have to have a good version of that available for you.
To those with pressing questions on the Javascript change, for people interested in doing a deep dive on some of the JavaScript "holes" we need to close, supported alternatives and roadmap please join us on our public Slack right here.
Harrison with our product team is looking to organize a deep dive session and needs your votes on when would work best to get together. That way we can also have more in depth discussions and follow up on our Slack. Thank you for your time and passion for Quickbase.
1. You will be able to still call the QB styles for buttons with the caveat that if we update or change the styles they would update for you. Bootstrap styles like the one here should also be just fine.
2. Iframes embedded on forms have been identified as one of the serious possible concerns so that is at the heart of them being locked down in this update. The product team is laser focused though on delivering a safe way to allow for embedding and there is already a working model of that in our new dashboards to allow a secure iframe.
@Adam Keever I see you are chatting with Ryan over on the community slack, he is probably best equipped to help you dig into the specifics of how you might do that one and get into all the requirements you would have to have a good version of that available for you.
To those with pressing questions on the Javascript change, for people interested in doing a deep dive on some of the JavaScript "holes" we need to close, supported alternatives and roadmap please join us on our public Slack right here.
Harrison with our product team is looking to organize a deep dive session and needs your votes on when would work best to get together. That way we can also have more in depth discussions and follow up on our Slack. Thank you for your time and passion for Quickbase.