Repository navigation
fix(aio): improve heading-anchor placement - #16336
petebacondarwin wants to merge 4 commits into
Conversation
|
The angular.io preview for ad70ba06950170b67f9e069dfd1e6a724ecaf1a3 is available here. |
|
docs_test fails (it seems that some assertions need to be updated). |
|
Good old tests :-) |
ad70ba0 to
2eb8cf9
Compare
|
Fixed the tests. |
|
Not super-excited about having them on the right, but other than that it LGTM (as long as Travis is happy). |
|
The angular.io preview for 2eb8cf91b5489990e32bbf403c645fa35ab9e8ff is available here. |
2eb8cf9 to
ad27107
Compare
|
I noticed that @sjtrimble's new PR (#16327) puts a heading anchor on the far right (and doesn't make it invisible when not hovering. This may have been my accident but it looked quite nice. (I also took this as an opportunity to fix the concern that @gkalpak had about the absolute positioning of icons by a generic CSS rule was too broad). Let me know what you think. |
|
The angular.io preview for ad27107e356032f2474c204dcf84b974f0cdb0ad is available here. |
|
I am not a huge fan of far-right, always-visible anchors (but I can live with that if we can't find a better solution). Here's another idea: |
gkalpak
left a comment
There was a problem hiding this comment.
Implementation-wise LGTM (with the tests fixed) 👍
|
I just realised this breaks copy button positioning. At least on my phone
…On Wed, 26 Apr 2017, 11:29 George Kalpakas, ***@***.***> wrote:
***@***.**** approved this pull request.
Implementation-wise LGTM (with the tests fixed) 👍
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#16336 (review)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAA9JwsKcoAu9nizD3B9m4ArIQpfKy52ks5rzxxygaJpZM4NIehE>
.
|
There was a problem hiding this comment.
This should probably be right: 0.
|
I don't see any difference with this PR (vs master). Positioning on mobile is probably already broken (see https://github.com/angular/angular/pull/16336/files#r113424809). |
|
I fixed the mobile alignment. And I also made it invisible again. |
|
The angular.io preview for 8dbca6afbf7cfb0770d3b4491b8322bf48e669d2 is available here. |
|
@petebacondarwin It wasn't my intent to put the anchor on the right :) but I know this might fix some of the header indentation issues for now. The side effect of your updates is having the h1 before element (the line under the h1) extend a bit further out than planned. Can we make the width 10% instead? |
|
Let's check this is what we actually want before you make any more changes
…On Wed, 26 Apr 2017, 17:11 Stefanie Fluin, ***@***.***> wrote:
@petebacondarwin <https://github.com/petebacondarwin> It wasn't my intent
to put the anchor on the right :) but I know this might fix some of the
header indentation issues for now. The side effect of your updates is
having the h1 before element (the line under the h1) extend a bit further
out than planned. I will submit an update.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#16336 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAA9J-zB5Vx0wyHFi4kj7ahnC4QeMSb7ks5rz2xrgaJpZM4NIehE>
.
|
|
In our meeting we agreed to move the anchor back to the left side and change the CSS so that if the heading is inside a subsection the anchor is moved further left so that from a user's perspective the anchor always appears in the left gutter of the page. |
8dbca6a to
dc8b9d4
Compare
|
The angular.io preview for dc8b9d4423cd66f4bc7b9fa4bfbb4ae79214676e is available here. |
|
@petebacondarwin I like the new anchor-in-the-gutter. Looking forward to seeing it work with HTML heading tags as well as MD heading tags. Thanks! |
This package will allow us to do complex post-processing on the HTML that is rendered by Nunjucks.
Previously the CSS styling for material icons was too broad and affected all instances of icons. This commit constrains the position of copy button icons only to copy buttons.
The autolinking is now done on the `renderedContent` which means it also captures and autolinks headings that were generated outside of markdown.
dc8b9d4 to
e5f23ae
Compare
| /* Support for all WebKit browsers. */ | ||
| -webkit-font-smoothing: antialiased; | ||
| /* Support for Safari and Chrome. */ | ||
| text-rendering: optimizeLegibility; |
| * | ||
| * Each plugin is a factory function that will be called with the "rehype" engine as `this`. | ||
| * The factory should return a function that takes a HAST and returns a `boolean` or `undefined`. | ||
| * The HAST can be mutated by the this function. |
There was a problem hiding this comment.
The this variable
There was a problem hiding this comment.
I still think you meant "The HAST can be mutated by this function(where "this function" is the _"function that takes a HAST and returns abooleanorundefined`"_, which in turn is returned by the plugin factory function) 😁
There was a problem hiding this comment.
Oh yeah :-)
The autolinking is now done on the `renderedContent` which means it also captures and autolinks headings that were generated outside of markdown. PR Close angular#16336
The autolinking is now done on the `renderedContent` which means it also captures and autolinks headings that were generated outside of markdown. PR Close angular#16336
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
No description provided.