# Trigger on blur does not work

**URL:** <https://community.weweb.io/t/trigger-on-blur-does-not-work/16442>\
**Category:** Ask us anything\
**Created:** [February 13, 2025, 10:49am UTC](https://community.weweb.io/t/trigger-on-blur-does-not-work/16442 "2025-02-13T10:49:22Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vitor](https://avatars.discourse-cdn.com/v4/letter/v/c89c15/32.png) [@Vitor](https://community.weweb.io/u/Vitor)\
**Post date:** [February 13, 2025, 10:49am UTC](https://community.weweb.io/t/trigger-on-blur-does-not-work/16442/1 "2025-02-13T10:49:22Z")

</div>

I have some inputs that use this type of trigger and they were working correctly and you don’t start them, any changes due to the update?

---

<div class="post-metadata">

**Author:** ![DanielL](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/daniell/32/13398_2.png) [@DanielL](https://community.weweb.io/u/DanielL)\
**Post date:** [February 14, 2025, 11:28am UTC](https://community.weweb.io/t/trigger-on-blur-does-not-work/16442/2 "2025-02-14T11:28:03Z")

</div>

Hi, I can’t reproduce the issue. Can you try logging the event?

---

<div class="post-metadata">

**Author:** ![shrihari\_ap](https://avatars.discourse-cdn.com/v4/letter/s/6f9a4e/32.png) [@shrihari\_ap](https://community.weweb.io/u/shrihari_ap)\
**Post date:** [February 14, 2025, 11:50am UTC](https://community.weweb.io/t/trigger-on-blur-does-not-work/16442/3 "2025-02-14T11:50:01Z")

</div>

I’m facing this issue as well. It specifically does not work with the input type is set to number of decimal.

---

<div class="post-metadata">

**Author:** ![DanielL](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/daniell/32/13398_2.png) [@DanielL](https://community.weweb.io/u/DanielL)\
**Post date:** [February 14, 2025, 11:53am UTC](https://community.weweb.io/t/trigger-on-blur-does-not-work/16442/4 "2025-02-14T11:53:51Z")

</div>

What makes you say that? Can you provide more information, screenshot, or a screen recording? Can you try to use the Log action to log the event from the trigger?

---

<div class="post-metadata">

**Author:** ![shrihari\_ap](https://avatars.discourse-cdn.com/v4/letter/s/6f9a4e/32.png) [@shrihari\_ap](https://community.weweb.io/u/shrihari_ap)\
**Post date:** [February 14, 2025, 12:02pm UTC](https://community.weweb.io/t/trigger-on-blur-does-not-work/16442/5 "2025-02-14T12:02:51Z")

</div>

Check this video → [Lancers' Club | WeWeb - Google Chrome - 14 February 2025 | Loom](https://www.loom.com/share/81e9c524eeea4325b54754891687725d?sid=d21480b8-3028-45a9-99bb-727f77e5133e)

---

<div class="post-metadata">

**Author:** ![DanielL](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/daniell/32/13398_2.png) [@DanielL](https://community.weweb.io/u/DanielL)\
**Post date:** [February 14, 2025, 12:31pm UTC](https://community.weweb.io/t/trigger-on-blur-does-not-work/16442/6 "2025-02-14T12:31:22Z")

</div>

thanks, we are working on a fix

---

<div class="post-metadata">

**Author:** ![shrihari\_ap](https://avatars.discourse-cdn.com/v4/letter/s/6f9a4e/32.png) [@shrihari\_ap](https://community.weweb.io/u/shrihari_ap)\
**Post date:** [February 14, 2025, 12:38pm UTC](https://community.weweb.io/t/trigger-on-blur-does-not-work/16442/7 "2025-02-14T12:38:00Z")

</div>

Would you have an ETA ? This is a blocker for me !

---

<div class="post-metadata">

**Author:** ![Philip1](https://avatars.discourse-cdn.com/v4/letter/p/b5ac83/32.png) [@Philip1](https://community.weweb.io/u/Philip1)\
**Post date:** [March 5, 2026, 12:59pm UTC](https://community.weweb.io/t/trigger-on-blur-does-not-work/16442/8 "2026-03-05T12:59:57Z")

</div>

Is this already fixed? I’m having the same issue…

---

<div class="post-metadata">

**Author:** ![Joyce](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/joyce/32/13232_2.png) [@Joyce](https://community.weweb.io/u/Joyce)\
**Post date:** [March 12, 2026, 10:40am UTC](https://community.weweb.io/t/trigger-on-blur-does-not-work/16442/9 "2026-03-12T10:40:02Z")

</div>

Hi @Philip1 👋

I’m not 100% sure. We pushed a fix on a similar ticket but I’m not sure it fixed that exact issue.

If you haven’t already, would you mind [creating a bug ticket here](https://support.weweb.io/?category=bug) so the team can investigate further?
