Fix input-popover bug in docs

[cmslewis]

PR checklist

• Addresses an existing issue: Popover doesn't behave correctly when it has an autofocus'd input inside it  #240
• Bugfix
  • Includes tests
• Documentation update

What changes did you make?

In the Blueprint docs for <Popover>s:

• Disabled autofocus in the "Input" example to fix a weird scrolling bug

Is there anything you'd like reviewers to focus on?

[adidahiya]

this is awkward; should .pt-slider just get a min-width instead?

[giladgray]

yes i think that's the better solution. other inputs set their own widths so slider can follow suit. it'll make everyone's lives easier. there have been other issues reported with slider sizing (i think internally)

[cmslewis]

Went ahead and did this in a separate, self-contained PR: #266

[cmslewis]

@adidahiya @giladgray - changed the scope of this PR to just fix the input-popover issue; the slider-popover issue is fixed in the self-contained #266, since it went beyond a simple docs fix.

[blueprint-bot]

Fix whitespace error

Preview: docs | table Coverage: core | datetime

[blueprint-bot]

Remove hardcoded-width parent for slider popover example

Preview: docs | table Coverage: core | datetime

[llorca]

@cmslewis I feel like the autofocus on the input makes for a good example. Isn't the scrolling bug related to PR #187?

[cmslewis]

@llorca Should we merge this as a quick fix for the rank brokenness of that example, then revisit? Alternative is to leave it in place as a reminder, but I feel like the issue/PR here in Github can track that for us.

EDIT: I checked out the preview for #187. That does fix the issue with the input popover.

[giladgray]

i think position: fixed on overlays should resolve this issue, but we won't know till we try!

[cmslewis]

Closed in favor of a better fix with position: fixed.