+
Skip to content

Look at pragmatic ways to respect browser font-size #3

@joejoseph00

Description

@joejoseph00

Use case scenario:

Possible fixes:

Look at the change that was made to bootstrap 4

twbs#17070

Consider adding a shim.

Investigate providing an optional override for those who wish to shim in a solution on top of bootstrap 3. An additional CDN with the shim could be provided as an option. Consumers of this library could include this option by default for new installs.

Either way, I'm confident that there's a pragmatic low or no disruption path forward.

What type of a proposal to consider?

A pragmatic solution in this case refers to a low impact update to the project that will minimize disruption to it's stakeholders. It could be in the form of a carefully curated upgrade to the library it'self in a new branch which would target a future 3.5.x upgrade. Alternatively it could mean an optional shim to an existing 3.4.x. Serious proposals will be considered.

Path forward

a new branch/ release 3.5.0 can resolve this. A minimalist curated backport of the bs4/bs5 approach is well within the rhealm of possible. There are several possible ways forward to evaluate that have not yet been tabled.

Background information

  • TBD

Get a better understanding of the issue.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    点击 这是indexloc提供的php浏览器服务,不要输入任何密码和下载