[Extensibility Request] Allow extending available font sizes in RichContent editor (sizes 5-7)
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 45/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
调研方向
The issue names the standard Business Central RichContent control but no source file or test. Start by locating how RichContent is exposed and extended in this repository. Done means partners can add font sizes, extend the defaults, or replace the default size list while keeping the standard control.
由索引模型根据 Issue 内容生成。
描述
We are using the standard Business Central RichContent control:
field(IAX_HTMLContent; IAX_HTMLContent)
{
ExtendedDatatype = RichContent;
MultiLine = true;
}
The RichContent editor currently exposes only a limited number of font sizes through the toolbar.
For several customer scenarios, especially document templates and formatted public-sector communication, lower font sizes are required.
We would like to request an extensibility point that allows partners to extend or override the list of selectable font sizes.
Requested extensibility
Allow extensions to:
Add custom font sizes
Extend the default font-size list
Override the default list completely
Example:
Current: 1, 2, 3, 4
Requested: 1, 2, 3, 4, 5, 6, 7
Reason
The RichContent editor is a standard Microsoft control.
Without an extensibility point, partners must either accept the limitation or replace the editor with a custom solution.
An event or similar extensibility mechanism would allow partners to support additional font sizes while continuing to use the Microsoft standard control.
Business value
Keeps customers on the standard RichContent implementation
Reduces need for custom editors
Improves partner extensibility
No impact on existing customers
Fully backward compatible
Additional information
This request originates from Microsoft Support case:
TrackingID#2610271420001478
Microsoft Support recommended opening a GitHub request for an event/extensibility point.
- 主要语言
- PowerShell
- 星标
- 889
- 派生
- 285
- 平均合并
- 4 小时 7 分钟
- 30 天内合并 PR
- 1
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
microsoft/AL 的其他 Issue
-
accepted al-tools bug
难度 2/5 1-3 小时 新手友好度 72/100
-
难度 4/5 3-5 天 新手友好度 35/100
-
难度 4/5 3-5 天 新手友好度 48/100
-
难度 4/5 1-2 天 新手友好度 45/100
-
难度 1/5 1 小时以内 新手友好度 25/100
相似的 Issue
-
bug CI documentation good first issue help wanted P2
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复
-
bug good first issue
难度 1/5 1 小时以内 新手友好度 88/100
libredb/libredb-studio#2151 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
bug factory factory:unowned infrastructure ralph-priority:medium ralph-status:pending ralph-task
难度 2/5 1-3 小时 新手友好度 72/100
JoshCLWren/comic-pile#4483 ·
维护者通常 1 天内回复