Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ui.input demo page broken #1616

Closed
natankeddem opened this issue Sep 13, 2023 · 1 comment · Fixed by #1617
Closed

ui.input demo page broken #1616

natankeddem opened this issue Sep 13, 2023 · 1 comment · Fixed by #1617
Labels
bug Something isn't working
Milestone

Comments

@natankeddem
Copy link
Contributor

Description

At first I thought it was something on my end but I think this is legitimate. On https://nicegui.io/documentation/input you will notice only the first demo populates correctly. I tried it locally and got the same behaviour with these errors in the console. Other demos might also be affected, I didn't check all of them.

c:\PythonWs\ngd99\nicegui\website\intersection_observer.py:18: RuntimeWarning: coroutine 'more.<locals>.autocomplete_demo' was never awaited
  handle_event(self.on_intersection, UiEventArguments(sender=self, client=self.client))
RuntimeWarning: Enable tracemalloc to get the object allocation traceback
c:\PythonWs\ngd99\nicegui\website\intersection_observer.py:18: RuntimeWarning: coroutine 'more.<locals>.clearable' was never awaited
  handle_event(self.on_intersection, UiEventArguments(sender=self, client=self.client))
RuntimeWarning: Enable tracemalloc to get the object allocation traceback
c:\PythonWs\ngd99\nicegui\website\intersection_observer.py:18: RuntimeWarning: coroutine 'more.<locals>.styling' was never awaited
  handle_event(self.on_intersection, UiEventArguments(sender=self, client=self.client))
RuntimeWarning: Enable tracemalloc to get the object allocation traceback

It appears to be caused from this commit:
f253d9f

@rodja rodja added this to the 1.3.14 milestone Sep 14, 2023
@rodja rodja added the bug Something isn't working label Sep 14, 2023
@rodja rodja linked a pull request Sep 14, 2023 that will close this issue
@falkoschindler
Copy link
Contributor

As I just commented on #1617, it is so good you spotted this issue, @natankeddem!
And I agree that f253d9f ultimately caused the bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants