Ferenc
For some reason the title in the browser tab is always behind the dom/page rendering like 500 ms or something.
But the same is also a thing is in Next and SvelteKit, not sure about Livewire.
Can it be make to render at the same time as the page?
Trending in Questions
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
Hello,
I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
Documentation
While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
So my question is quite simple and i have found no conclusive answer on forum, google or AI.
Should we use :erlang.float for Integer to ...
New
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
Other Trending Topics
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hi there! We created Gust: A task orchestrator inspired by Airflow.
For those who have never heard about Aiflow, it’s a Python-based wor...
New
Hi everyone!
The first release candidate for the Expert language server project is now available!
We’ve published a press release detai...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #security










Showing Posts 1 to 4- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
arcanemachine
Sounds like a browser issue. Does this happen in multiple different browsers?
Ferenc
Yeah, it’s happening only in Chrome and Brave for some reason. Safari and Firefox do update the title in tab instantly as it should be.
Even in Brave when I am using no extensions and turn off the brave shield it’s still changed in tab like 300 - 400 ms later unlike in Safari or Firefox where the change is instant.
garrison
Looks like LiveView simply sets
document.title, but the invocation is wrapped inrequestAnimationFrame.Just a hunch: perhaps the animation frame callback is taking a while for some reason?
Try writing some JS to update
document.titlewith and without arequestAnimationFramecallback and see if you can reproduce that behavior.Another possibility is that work done by the LiveView JS (diff-related?) takes a long time after the callback is set, thereby delaying it. It would have to be a browser-specific performance issue I suppose. Make sure you test these things without any other tabs running in case that has something to do with it.
garrison
Just realized I may have misread this. Are you saying you observe the same delayed behavior in these other frameworks? If so I assume this is just chromium behavior and there’s nothing you can do, right?