# Breaking changes on clickability and date-times retrieved from page URL **URL:** \ **Category:** Announcements\ **Created:** [February 10, 2022, 8:24pm UTC](https://forum.bubble.io/t/breaking-changes-on-clickability-and-date-times-retrieved-from-page-url/191075 "2022-02-10T20:24:47Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![grace.hong](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/grace.hong/32/109318_2.png) [@grace.hong](https://forum.bubble.io/u/grace.hong)\ **Post date:** [February 10, 2022, 8:24pm UTC](https://forum.bubble.io/t/breaking-changes-on-clickability-and-date-times-retrieved-from-page-url/191075/1 "2022-02-10T20:24:47Z")
Hi everyone, We’re releasing a few bug fixes that we want to flag for you as they’re breaking changes. **Enforcing non-clickability for “This element isn’t clickable” property** Let’s say you have Element A, which has “This element isn’t clickable” checked and doesn’t have its own workflow. Element A is inside Element B, which does have a workflow and is clickable. In the past, you would be able to click on Element A, which would trigger the workflow on its parent element (Element B) as “This element isn’t clickable” wasn’t truly being enforced. We’re now actually enforcing “This element isn’t clickable” on elements, so in the situation above, Element A would not be clickable, and no workflow would run. If you do have child elements like Element A that were allowing clicks before and ran workflows on their parent elements, you can simply uncheck the “This element isn’t clickable” box on the child element to return to prior behavior. **Date-times from “Get data from page URL”** Previously, when using the action “Get data from page URL" to retrieve an ambiguous date-time that didn’t specify timezone (ex. 31 Dec 2014 23:59:59), the interpretation of the date-time was different on the client versus server. The server interpreted the date-time in UTC versus the client interpreting the date-time in the user’s current timezone. Since other date-time inputs on Bubble interpret date-times using the user’s current timezone, we have made this behavior consistent on “Get data from page URL,” so it now will interpret these ambiguous date-times from the URL in the user’s current timezone. You can change this interpretation (to be interpreted in a different timezone) by adding/subtracting time to the entered date-time. ---
**Author:** ![josh10](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/josh10/32/82900_2.png) [@josh10](https://forum.bubble.io/u/josh10)\ **Post date:** [February 10, 2022, 9:11pm UTC](https://forum.bubble.io/t/breaking-changes-on-clickability-and-date-times-retrieved-from-page-url/191075/2 "2022-02-10T21:11:18Z")
What if we have the following scenario? Group A (clickable) Holding Group B (clickable) Holding group C (not clickable) Does Group A inherit all the way down from group C? ---
**Author:** ![grace.hong](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/grace.hong/32/109318_2.png) [@grace.hong](https://forum.bubble.io/u/grace.hong)\ **Post date:** [February 10, 2022, 9:38pm UTC](https://forum.bubble.io/t/breaking-changes-on-clickability-and-date-times-retrieved-from-page-url/191075/3 "2022-02-10T21:38:34Z")
So just to be clear, Group C is the parent of Group B, which is the parent of Group A? In that situation, Group A would _not_ inherit non-clickability from Group C. You would need to mark the checkbox for “this element isn’t clickable” for Group A if you want it to be non-clickable. Here’s how you can think of how this change impacts elements nested in groups: A click on a child element travels outwards/upwards to parents, until either: - It hits something that isn’t clickable, and stops going - It hits something that has a “when this element is clicked” workflow, and runs the workflow - It runs out of elements to check - It hits a workflow Therefore, if all the groups you mentioned have workflows that run when clicked, clicking on Group A will run Group A’s workflow; clicking on Group B will run Group B’s workflow; and clicking on Group C will not do anything (it is not clickable). Let’s say you have another group (Group D) that is the parent of Group C (and everything within) and Group D is clickable and has a workflow that runs on click. Clicking on Groups A and B (and Group C which is non-clickable) will not run Group D’s workflow since Groups A and B are inside of a parent group (Group C) that is non-clickable. You can only run Group D’s workflow by clicking on Group D. Hope this clears it up! ---
**Author:** ![sudsy](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/sudsy/32/114637_2.png) [@sudsy](https://forum.bubble.io/u/sudsy)\ **Post date:** [February 10, 2022, 10:46pm UTC](https://forum.bubble.io/t/breaking-changes-on-clickability-and-date-times-retrieved-from-page-url/191075/4 "2022-02-10T22:46:35Z")
> [@grace.hong](#): > > Enforcing non-clickability for “This element isn’t clickable” property Nice. I no longer have to create empty workflows for inner groups to keep the event from bubbling up the hierarchy. Plus, the mouse pointer now properly reflects the “clickability”. Double win. 👍 ---
**Author:** ![fabrice.latour04](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/fabrice.latour04/32/111451_2.png) [@fabrice.latour04](https://forum.bubble.io/u/fabrice.latour04)\ **Post date:** [February 10, 2022, 11:26pm UTC](https://forum.bubble.io/t/breaking-changes-on-clickability-and-date-times-retrieved-from-page-url/191075/5 "2022-02-10T23:26:19Z")
When using Icons (i.e., Googles Material Icons and Font Awesome Icons) in groups that have a Workflow, Icons no longer show a clickable pointer even though the Icon doesn’t have a Workflow. Text elements still function correctly. ![gif](https://us1.discourse-cdn.com/bubble/original/3X/2/a/2a7d36c9d03ef6ba02691129f73e0757e57e7558.gif) ---
**Author:** ![yorgio1024](https://avatars.discourse-cdn.com/v4/letter/y/f17d59/32.png) [@yorgio1024](https://forum.bubble.io/u/yorgio1024)\ **Post date:** [February 11, 2022, 12:33am UTC](https://forum.bubble.io/t/breaking-changes-on-clickability-and-date-times-retrieved-from-page-url/191075/6 "2022-02-11T00:33:33Z")
This update broke my live app, how revert this update?, bubble it should implement this changes to update manually. Im disappointing with this because cannt deploy a new version right now and cannt control the update ---
**Author:** ![sudsy](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/sudsy/32/114637_2.png) [@sudsy](https://forum.bubble.io/u/sudsy)\ **Post date:** [February 11, 2022, 1:27am UTC](https://forum.bubble.io/t/breaking-changes-on-clickability-and-date-times-retrieved-from-page-url/191075/7 "2022-02-11T01:27:56Z")
> [@fabrice.latour04](#): > > Icons no longer show a clickable pointer **Button** elements as well. Oddly, **Link** elements configured as **not** clickable **do** display the clickable pointer and trigger the workflow up the hierarchy. I’ve submitted a bug report. ---
**Author:** ![fabrice.latour04](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/fabrice.latour04/32/111451_2.png) [@fabrice.latour04](https://forum.bubble.io/u/fabrice.latour04)\ **Post date:** [February 11, 2022, 1:40am UTC](https://forum.bubble.io/t/breaking-changes-on-clickability-and-date-times-retrieved-from-page-url/191075/8 "2022-02-11T01:40:38Z")
Yeah, this change is actually causing more problems than fixing ones. Also, seeing strange behaviors with [Drag and Drop elements](http://forum.bubble.io/t/update-apr-28-sortable-rg-drag-drop-plugin-by-ezcode/85730/217) and finding myself needing to use CSS on every icon and button that don’t have a Workflow 😅. Hope they revert back or change it fast. `.no-click {pointer-events: none !important;}` ---
**Author:** ![ben29](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/ben29/32/102546_2.png) [@ben29](https://forum.bubble.io/u/ben29)\ **Post date:** [February 11, 2022, 3:21am UTC](https://forum.bubble.io/t/breaking-changes-on-clickability-and-date-times-retrieved-from-page-url/191075/9 "2022-02-11T03:21:39Z")
> **[Scoreboard 2/11/22 | Takeside News](https://news.takeside.io/version-test/scoreboard-and-standings?date=Feb%2B11%2C%2B2022%2B12%3A00%2Bam&init=1)** > > Check out NBA schedules for all upcoming games. View conference standings and in depth team statistics. Compare East vs West. Stay in the know Every single time on this page just broke. It’s now adding 5 hours to my UTC time… ---
**Author:** ![ben29](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/ben29/32/102546_2.png) [@ben29](https://forum.bubble.io/u/ben29)\ **Post date:** [February 11, 2022, 3:22am UTC](https://forum.bubble.io/t/breaking-changes-on-clickability-and-date-times-retrieved-from-page-url/191075/10 "2022-02-11T03:22:32Z")
Not to mention that link now sends you to the wrong day… Huge issue tbh ---
**Author:** ![ben29](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/ben29/32/102546_2.png) [@ben29](https://forum.bubble.io/u/ben29)\ **Post date:** [February 11, 2022, 3:33am UTC](https://forum.bubble.io/t/breaking-changes-on-clickability-and-date-times-retrieved-from-page-url/191075/11 "2022-02-11T03:33:44Z")
Adding to the odd behaviour… clicking the previous day arrow now sends you back 2 days. ---
**Author:** ![sudsy](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/sudsy/32/114637_2.png) [@sudsy](https://forum.bubble.io/u/sudsy)\ **Post date:** [February 11, 2022, 3:37am UTC](https://forum.bubble.io/t/breaking-changes-on-clickability-and-date-times-retrieved-from-page-url/191075/12 "2022-02-11T03:37:38Z")
> [@yorgio1024](#): > > bubble it should implement this changes to update manually. I have to agree. In fact, I thought it was Bubble’s policy for all breaking changes to be opt-in. It used to be that way, as mentioned in [the following post from several years ago](http://forum.bubble.io/t/breaking-change-invisible-text-elements-now-collapse/38334)… > [@Breaking change - Invisible text elements now collapse](https://forum.bubble.io/t/breaking-change-invisible-text-elements-now-collapse/38334/1): > > As with all breaking changes, this new functionality is opt-in […] ---
**Author:** ![ben29](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/ben29/32/102546_2.png) [@ben29](https://forum.bubble.io/u/ben29)\ **Post date:** [February 11, 2022, 3:46am UTC](https://forum.bubble.io/t/breaking-changes-on-clickability-and-date-times-retrieved-from-page-url/191075/13 "2022-02-11T03:46:52Z")
Praying they revert on this update ASAP. ---
**Author:** ![soh.ju.hu](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/soh.ju.hu/32/25563_2.png) [@soh.ju.hu](https://forum.bubble.io/u/soh.ju.hu)\ **Post date:** [February 11, 2022, 4:19am UTC](https://forum.bubble.io/t/breaking-changes-on-clickability-and-date-times-retrieved-from-page-url/191075/14 "2022-02-11T04:19:25Z")
This update truly broke my site too! I have to figure what I have to do now! 😭 ---
**Author:** ![bcart0v](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/bcart0v/32/73592_2.png) [@bcart0v](https://forum.bubble.io/u/bcart0v)\ **Post date:** [February 11, 2022, 5:43am UTC](https://forum.bubble.io/t/breaking-changes-on-clickability-and-date-times-retrieved-from-page-url/191075/15 "2022-02-11T05:43:30Z")
I just realized this has broken the functionality of my app too. Creating an appointment from one page to another drastically changes the arrival/departure time, which isn’t ideal in an appointment based app… I’m going to have to send a lot of emails tomorrow. ---
**Author:** ![ryanck](https://avatars.discourse-cdn.com/v4/letter/r/13edae/32.png) [@ryanck](https://forum.bubble.io/u/ryanck)\ **Post date:** [February 11, 2022, 7:00am UTC](https://forum.bubble.io/t/breaking-changes-on-clickability-and-date-times-retrieved-from-page-url/191075/16 "2022-02-11T07:00:23Z")
Hello @grace.hong But you guys did not implement this without asking the users right? I mean we will need to hit the upgrade button to get this going. Thanks. ---
**Author:** ![chad](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/chad/32/89415_2.png) [@chad](https://forum.bubble.io/u/chad)\ **Post date:** [February 11, 2022, 7:44am UTC](https://forum.bubble.io/t/breaking-changes-on-clickability-and-date-times-retrieved-from-page-url/191075/17 "2022-02-11T07:44:45Z")
Why would you tell people this after the fact. Why wouldn’t you let people know ahead of time… It’s pretty disrespectful to be honest ---
**Author:** ![chad](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/chad/32/89415_2.png) [@chad](https://forum.bubble.io/u/chad)\ **Post date:** [February 11, 2022, 7:45am UTC](https://forum.bubble.io/t/breaking-changes-on-clickability-and-date-times-retrieved-from-page-url/191075/18 "2022-02-11T07:45:22Z")
Perhaps provide some instructions on how to fix it, when the change will become live… ---
**Author:** ![oliviercoolen](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/oliviercoolen/32/70368_2.png) [@oliviercoolen](https://forum.bubble.io/u/oliviercoolen)\ **Post date:** [February 11, 2022, 7:54am UTC](https://forum.bubble.io/t/breaking-changes-on-clickability-and-date-times-retrieved-from-page-url/191075/19 "2022-02-11T07:54:48Z")
Yup experiencing the same here, what a bummer! ---
**Author:** ![mikeloc](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/mikeloc/32/93001_2.png) [@mikeloc](https://forum.bubble.io/u/mikeloc)\ **Post date:** [February 11, 2022, 9:38am UTC](https://forum.bubble.io/t/breaking-changes-on-clickability-and-date-times-retrieved-from-page-url/191075/20 "2022-02-11T09:38:51Z")
@grace.hong, @bubble… individual threads are coming in, too. > [@PLEASE Revert todays change made to time zones. It just nuked my entire app](http://forum.bubble.io/t/please-revert-todays-change-made-to-time-zones-it-just-nuked-my-entire-app/191105): > > Whatever changes were made to the timezone behavior in bubble is destroying my app. All times are now incorrect (set to current users timezone with a UTC input) and sending links with certain page params sends actually ends up linking to the previous day. Whatever update was made here: [Breaking changes on clickability and date-times retrieved from page URL](http://forum.bubble.io/t/breaking-changes-on-clickability-and-date-times-retrieved-from-page-url/191075) Is causing tons of issues. > [@Why changes “this element isn’t clickable” behavior? on Feb 11,2022](http://forum.bubble.io/t/why-changes-this-element-isn-t-clickable-behavior-on-feb-11-2022/191130): > > Why change “this element isn’t clickable” behavior? All of the grouped buttons and grouped icons became unclickable. which means the button and icon with an unclickable setting placed in a clickable group are now are became unclickable. I will need to change the setting one by one. Smart money says these changes get reverted pretty quickly… definitely seems like they should have been opt-in. Edit: Likely another one. > [@Can not click on items](http://forum.bubble.io/t/can-not-click-on-items/191141): > > Suddenly my app disfunctions. I cannot click on thing in my app or create textst in input field. haven’t changed anything in my app, but my customers are complaining now Bubble running oke??? Edit: And another from someone who was already active in this thread, so you know it ain’t good. > [@Recent changes destroyed my app. How to revert?](http://forum.bubble.io/t/recent-changes-destroyed-my-app-how-to-revert/191148): > > Hello The changes you published recently destroyed the functionality of my whole app. I would kindly like to ask the team if we can have control over the updates we want to have. Personally this update destroyed a lot of relations we have with our customers. Is it time to build a real app? Is bubble still realiable? Please let us know what are you guys planning. Thank you [Next page](https://forum.bubble.io/t/breaking-changes-on-clickability-and-date-times-retrieved-from-page-url/191075.md?page=2)