This issue occurs on the 3.3.5 branch as well.

@seanlip Hello! I believe I have resolved these console errors by changing where the values are set to be more similar to the way they were set when on the subTopic page. While doing so, I observed that the 'header text' and 'subheader text' values were not being displayed anywhere, despite being defined for the Mobile Screen due to the condition !WindowIsNarrow. Therefore, I removed the '!', added the condition to check if the title exists and corrected the display of those values on the frontend. Is this the desired outcome?
Could I be assigned this?

Before:

After:

@Sepremo Sorry for the late reply. I think what we would need to know, is what the cause of the original error is. Can you explain it? (Otherwise we cannot be sure that your fix addresses the root cause of the error.)

I'm also finding it hard to understand what exactly you changed and the reasoning behind it. Perhaps you could explain that in more detail?

Thanks!

@seanlip

@Sepremo Sorry for the late reply. I think what we would need to know, is what the cause of the original error is. Can you explain it? (Otherwise we cannot be sure that your fix addresses the root cause of the error.)

Certainly! The error occurred when attempting to open the Chapter Editor in the Story Editor. It appears that the headerText (along with subheaderText) property undergoes updates after Angular's change detection cycle has concluded. This behavior stems from the component managing the new Chapter Editor Tab. The issue arises because it alters a bound value (as bound in the top-navigation-bar.component.html) within a new Tab (Chapter Editor), albeit within the same page (Story Editor).

Upon further investigation, I noticed a similar scenario where opening a subTopic Editor tab from the Topic Editor page did not encounter this error. The disparity lies in how the headerText (and subheaderText) values were updated: in the TopicEditorRoutingService instead of within the subTopic Editor component, unlike the approach adopted by the Chapter Editor.

I'm also finding it hard to understand what exactly you changed and the reasoning behind it. Perhaps you could explain that in more detail?

To address the issue, I relocated the updates for the headerText and subheaderText values from the Chapter Editor component (story-node-editor.component.ts) to the equivalent in the Story Editor, specifically within the TopicEditorRoutingService (found in story-editor-navigation.service.ts). This adjustment aimed to ensure consistency and resolve the encountered error.

Upon further examination, I observed that these values failed to display even when I resized the screen to simulate a mobile device. I discovered that the values were not visible when the windowIsNarrow flag was set to true, which appeared contradictory. Consequently, I modified the display behavior to rectify this issue and addressed some display inconsistencies by refining the CSS in the Top Navigation Bar.
Is this the expected behavior?

Thanks!

You're welcome! I'm sorry if I explained anything poorly.

Thanks @Sepremo! This all sounds reasonable, feel free to create a PR. I'll assign you to the issue so that you can do that. Thanks!

@seanlip
Hello! I apologize for the delay in creating a PR. After completing a rebase without encountering any conflicts, it appears that my code is failing the MyPy checks (AssertionError: Cannot find component 'TraceDispatch' for 'prompt_toolkit.application.application.Application.TraceDispatch').
When checking each commit from my rebase, the error seems to appear when adding the Voice artist metadata audit and model creation job (#19742) commit. I am currently investigating to identify the root cause of the issue and will create a PR as soon as I can.