Failure using anchors to jump to appropriate fb object 
Autor: Esahc ..
Visitado 1772,
Seguidores 1,
Compartilhado 0
When there are multiple FB objects on a page each with their own anchor, the display always jumps to the bottom of the page irrespective of which anchor is selected.
I have attached a sample project to demonstrate the issue. It occurs even if each anchor is in the object above the fb object.
The anomoly was identified by John H in thread https://helpcenter.websitex5.com/pt/post/240044
After much frustration and with assistance from John S he now has an even better solution, but none the less the problem remains.
Publicado em
(It > En) hi, unfortunately I don't currently have the program to be able to test your IWZIP file...
...
... you could post your example online, so that I can evaluate it ...
... so I could also check if my EXTRA code might be compatible ...
... from the example of John you mentioned I understood that the problem in his case is only for the external anchors, and that in his case it always depends on the automatic height, not defined, so I advised him to try a fixed height of 550px, but was not able to implement it, or I had explained myself badly ...
... if it is not possible to assign a fixed height to the Facebook object, then you should try to assign this fixed height of 550px to any object positioned in the cell next to the Facebooks in the same row, for example an HTML Code Object containing "& nbsp ; " with a height of 550px ...
... this operation should create the placeholders of the page already arranged and defined at the opening of the same, regardless of the slowdown of the Facebook code ...
.
Hello, ciao
.
.
Hello Esahc
I am afraid that, as I believe was mentioned in the other topic by KolAsim too, this is an issue specific to Objects that load asynchronously which is inherently there for every browser and website, and not with website's generated by WebSite X5 specifically and it was stated by me on some other older topic, that this is something that we cannot, unfortunately, intervene on
Since all FB Objects load later than the time it takes for the browser to handle an anchor, moving the user to a specific point on a different page than the current one is simply hard to achieve.
This is due to how the anchors work in the browsers. Keep in mind that this anchor system is not something put up by us via code specifically for the software but relies on the fundamental anchor system of browsers.
When the page changes, the scroll position is to determine by where in the page the anchor is when the page opens. If the page takes time to load a different element, the scroll position will be wrong. There is simply no way around this
Anchors can be used to navigate a page internally and sometimes on new pages assuming all of the content is very static and nothing gets loaded later on. You can test this by filling a page with different content and trying it out
As of now, the workaround you found on the other topic works because it was made specifically for this occurrence, but it is not guaranteed to work in every circumstance and with every object which might suffer from the same issue
I hope I explained the issue thoroughly and remain available for clarification
Stefano