functions.js | A hub of numerous functions with various functionalities

I would suggest you to pass the values via some data-* attribute of each td.

This is tracked by issue https://github.com/npgsql/efcore.pg/issues/1674. It has already been fixed and will be released with version 5.0.7 of the EF Core PostgreSQL provider (which should come out in the next few days).

You'll have to set up a queue of messages, so that onMessage only places the input in the queue and defers its processing until later on. For example, you could make the queue a Promise with then as enqueue operation. This way it's guaranteed that no processing starts until all previous ones are completed.

Here's a small demo, a click on the button simulates an incoming message:

You can add it to the window object:

@connexo thanx a lot, i just found that if no path is given then path from the root is considered not the page's path is used. Any how, thanx for ur excellent guess and help.

i was missing the file path of .js file.

Pass the function externalObject.action itself as a parameter to doSomethingElse.

I don't think the functions.php file has anything to do with it - usually HTML structures like this are created in template php files which are in the themes folder - either on the top level of that folder or as "template parts" in an according subfolder. You have to edit those( or actually those among them that are used by the pages you are referring to), changing all

However, since any not-selfmade theme will be updated every now and then, those changes would be overwritten with updated files when available, it would be necessary to create a child theme, which only contains those templates which you want to change (see also https://developer.wordpress.org/themes/advanced-topics/child-themes/). Then again, updated themes might contain template updates which are necessary, so you'd always have to check which details were updated in that particular template file, integrating it into your child theme templates or editing the updated original themes and using them in your child theme.

P.S.: I think the title of your question is a bit misleading: In the question text you are asking about certain title tags in the product pages, not about parts of the menu, aren't you?

I found the solution

1. I removed the following

   if ('serviceWorker' in navigator) { window.addEventListener('load', function () { navigator.serviceWorker.register('flutter_service_worker.js'); }); }

2. I upgraded all the javascript links and launched again Firebase Initiates.

Just for the sake of answering this question I'm gonna put what fixed it in the end. Credit to geocodezip who helped me figure it out. Basically as geocodezip said the map was initialising before the posts were being added so the map div didn't exist in order to solve that I removed the callback on my API link and then wrapped the map code in a function and called them at the end of the snapshot