Font size does not work on input placeholder on Edge

Issue #4355171 • Assigned to Rossen A.


Aug 24, 2015
This issue is public.
Reported by 8 people

Sign in to watch or report this issue.

Steps to reproduce


Repro Steps:

Here’s the fiddle
The “font-size” property works correctly in IE 11 (using the -ms-input-placeholder pseudo element). Edge uses the -webkit pseudo element. However, while Edge applies the “color” property it ignores the "font-size".

See description.

Expected Results:

The “font-size” property does not work.

Actual Results:

Dev Channel specific:



0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Christian F.”

      Changed Assigned To to “Rossen A.”

      Changed Steps to Reproduce

    • Also encountering this error; Edge ignores font-size for placeholders.

      Any progress?

    • Hi,

      I am also facing this issue.

      So, Please can you let me know any expected time to fixed it.


    • The font-family seemingly can’t be changed on Edge, as well.

    • +1. Also cannot change font family in input placeholders in Edge.

    • +1 as well…cannot apply placeholder formatting using :-ms-input-placeholder, ::-ms-input-placeholder, or ::-webkit-input-placeholder. Formatting works in Chrome using the non-prefixed ::placeholder pseudo-selector.

    • For 2 years now and this bug is not fixed? Really???

    • :D
      I’ve reported this bug in another thread so they may look up at this again. See what response i got:

      Francois R. Mar 22, 2017 MICROSOFT EDGE TEAM
      I don’t see this as a bug. Placeholders should not use a different font size than the text they replace. We allow to control the color in cases when the author sets a background on the text input which makes the default placeholder color unsuitable. Resolving as By Design for now, but the issue is tracked in the database if we ever need to come back to this.

      By Design haha,
      never laughed so hard

    • I’ve listed a perfectly valid case for its use in the other thread. (

      I get that it’s not formalized specification, but they’ve already opened a can of worms by implementing it before (as have all the other browsers). Why regress on existing functionality?

    You need to sign in to your Microsoft account to add a comment.

    Sign in