[FW][FIX] BottomBarSheet: Rename a sheet with style content on Firefox

[fw-bot]

The issue addressed in PR #3351 unfortunately used a contentEditable value that is not compatible with Firefox 1

This revision implements the first strategy explored by the aforementioned PR by removing the full format from the contenteditable span when we stop the edition.

Testing required to define some properties as JSdom does not properly support the implementation of innerText (see 2)

Task: 3754944

Description:

description of this task, what is implemented and why it is implemented that way.

Task: : TASK_ID

review checklist

• feature is organized in plugin, or UI components
• support of duplicate sheet (deep copy)
• in model/core: ranges are Range object, and can be adapted (adaptRanges)
• in model/UI: ranges are strings (to show the user)
• undo-able commands (uses this.history.update)
• multiuser-able commands (has inverse commands and transformations where needed)
• new/updated/removed commands are documented
• exportable in excel
• translations (_t("qmsdf %s", abc))
• unit tested
• clean commented code
• track breaking changes
• doc is rebuild (npm run doc)
• status is correct in Odoo

Forward-Port-Of: #3894

[robodoo]

Pull request status dashboard.

[fw-bot]

@rrahir @LucasLefevre cherrypicking of pull request #3894 failed.

stdout:

Auto-merging tests/components/bottom_bar.test.ts
CONFLICT (content): Merge conflict in tests/components/bottom_bar.test.ts

stderr:

14:46:14.851133 git.c:463               trace: built-in: git cherry-pick c443de658aff251ad42eba6234a6aaaa5fe16e71
error: could not apply c443de658... [FIX] BottomBarSheet: Rename a sheet with style content on Firefox
hint: After resolving the conflicts, mark them with
hint: "git add/rm <pathspec>", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".
----------
status:

Either perform the forward-port manually (and push to this branch, proceeding as usual) or close this PR (maybe?).

In the former case, you may want to edit this PR message as well.

⚠️ after resolving this conflict, you will need to merge it via @robodoo.

More info at https://github.com/odoo/odoo/wiki/Mergebot#forward-port

[rrahir]

@robodoo r+