akveo / polymer-admin Goto Github PK

Now its position is unpredictable since it depends on the length of the page title. Text should never be able to displace and change to position of your app's principle navigation button.
Placing it after the title puts it further from the edge of the screen, which makes clicking it in mobile devices harder.
On mobile it's practically right aligned, but it opens a menu on the left, which makes no sense cognitively speaking because it's not connected to that side of the screen in any way.
And finally, because the Material Design spec says so:
https://www.google.com/design/spec/layout/structure.html#structure-app-bar

Hi ,

I'm very new to this , and I have few question .

How could I make http request ?
Should I Iron-Ajax ?

How to bind the response to some element ?

I am glad to have found your projects. Very clean and alluring.
I was testing the Polymer dash in the Other UI Elements section of this page, and after clicking the various buttons - when I clicked the Transitions button the screen was blacked out (with the right transparency and all). But, when I clicked to get out of the transition the screen returned to the original color and everything froze, and I am unable to navigate anywhere or click anything. Hitting the Esc didn't help either.
I'm using Chrome on a Win7. I also use Privacy Badger {big fan :} and disabled each warning (fonts etc) one at a time and did not have any success doing that test.
Thanks much!

pa-page-title elements use title attribute, which most browsers render as a useless tooltip:

I clicked through quickly on my nexus 6 in chrome and found numerous minor UI issues. The footer had overlapping text. The grid /list buttons did nothing. I went to the other UI elements page and clicked transitions, the dialog was about a dozen pixels high. Hitting the back button closed the dialog but left the overlay on the screen.