feat(overlay): add basic core of overlay

[jelbourn]

R: @hansl @kara

This is the first step on the journey to overlays. I'll be doing it in as small of pieces as possible for ease of reviewing. The PR covers adding an overlay element to the DOM and attaching a portal to it. Future PRs will cover styling, sizing, positioning, and helper directives.

[kara]

A few typos:
"Overlay are" --> "Overlays are"
"used as low-level a building building block" --> "used as a low-level building block"

[kara]

Still has "building" twice?

[kara]

LGTM, though still has that one typo if you want to fix

[hansl]

@robertmesserle: the e2e is failing on this; https://travis-ci.org/angular/material2/builds/117214613

[robertmesserle]

That means it’s working. He didn’t update the screenshot.

Sent from my iPhone

On Mar 20, 2016, at 5:15 PM, Hans [email protected] wrote:

@robertmesserle: the e2e is failing on this; https://travis-ci.org/angular/material2/builds/117214613

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

[jelbourn]

I did update it. Seems like it fails to get the image.

[robertmesserle]

@jelbourn Ah, my bad - I was looking on my phone earlier and didn't see the screenshot in the changed files. Must've missed it. Anyway, hard to say what is happening, but this is one of the first things that made me want to push for going back to the server idea for screenshots: our method of manually handling git-lfs files is definitely hacky and I wouldn't be surprised if that was the cause.

[robertmesserle]

Also, after looking at the screenshot URL, it's likely the issue I brought up earlier about PR's that live in other people's repos. The URL for your screenshot doesn't match the pattern of other screenshots we've dealt with so far, so manually handling the git-lfs files might not even really be a valid option.

[jelbourn]

@robertmesserle another bullet point for your doc.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}