"Enter" key inserts undesired styling

[Daniel Souza]

Hello,

With certain documents, we have noticed that pressing the "Enter" key at the start of a line will add undesired styles, such as bold. This happens regardless of wheter the current line has or not the bold property. I have made a simple example that demonstrates this behavior with the problematic document:

https://stackblitz.com/edit/7xxc69-taznpt?file=index.js

It is important to note that this will only happen on certain documents, so I believe this may be a problem with the given document. My first guess was that the section or other parent was declaring bold as true and the individual lines were all setting the bold to false. However, I have struggled to debug what is the matter with the SFDT, as it is not as straightforward as an HTML file, for instance. I have also tried converting the SFDT document to HTML using the DocumentServices, and that works fine. The converted HTML is simple and will only apply the bold property to the necessary elements. I have also added this html as `data.html` to the demo.

Could this be an issue with the document itself or the documentEditor? Any help is appreciated.

Best regards,

Daniel Souza

[Mohammed Affan Saqib Hussain]

Hi Daniel Souza,

We can able to reproduce the reported issue. Currently, we are validating the issue and get back to you with more details by October 04,2024.

Regards,

Mohammed Affan C

[Mohammed Kaif Shahul Hameed]

Hi Daniel Souza,

we have confirmed the reported issue ‘ "Enter" key inserts undesired styling’ as a defect and logged a defect report. We will fix this issue in our patch release, which is expected on October 22,2024.

You can track the status of the bug through the below feedback link:

https://www.syncfusion.com/feedback/61830/enter-key-inserts-undesired-styling

Disclaimer: “Inclusion of this solution in the weekly release may change due to other factors including but not limited to QA checks and works reprioritization.”

Regards,
Mohammed Kaif S

[Mohammed Kaif Shahul Hameed]

Hi Daniel Souza,

                       Sorry for the inconvenience. We have resolved the reported issue, but we are facing some breaks due to this in our automation testing, so we couldn’t include this fix in this release. We will include the fix in our upcoming patch release without further delay, which is scheduled for October 29, 2024. 

Regards,
Mohammed Kaif

[Niranjan Anumuthu]

Hi Daniel Souza,

 

We have attached the custom package with fix. Please find below the steps to use a custom package:

1. Extract the custom package from the below attachment.
2. Copy the items inside the folder.
3. Then go to the sample location, and then navigate to the folder node_modules\@syncfusion\. You can see the ej2-documenteditor folder. Also, remove the content inside the ej2-documenteditor folder in node_modules\@syncfusion\.
4. Then paste it inside the ej2-documenteditor folder.
5. Then build and run the project.

 

Note: Please don’t give npm install or npm update. It will refresh the whole package.

We will include this fix in our upcoming release which is scheduled to release on November 5, 2024. Until then, kindly use the attached custom package.

Attachment: syncfusionej2documenteditor27.1.48_fbd331d.zip

[Daniel Souza]

Hello Niranjan, 

Thank you for your response.
Unfortunately we would not be able to test the solution until it is released as a new version of the npm package. 
That being said, it should not be a problem for us to wait until November 5.

Thank you for your attention to this matter.

Best regards, 
Daniel

[Aravind Dharani]

Daniel Souza,

We will update the patch release details on Nov 05, 2024.

Regards,

Aravind D

[Niranjan Anumuthu]

Hi Daniel Souza,

Due to technical issue, we could not able to include the fix in this weekly patch release. We will include this issue in our upcoming 2024 Volume 3 SP1 release, which is expected to release at mid of November. Until then please use the custom package for the fix. We appreciate your patience until then.

Regards,

Niranjan N A