-
Notifications
You must be signed in to change notification settings - Fork 277
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(site): anchor offset #1460
fix(site): anchor offset #1460
Conversation
@GaoNeng-wWw is attempting to deploy a commit to the OpenTiny Team on Vercel. A member of the Team first needs to authorize it. |
* fix(tree-menu): [tree-menu] fix search issues * fix(test): [ip-address,rate] update e2e test
* feat(drawer): fit x-design theme * feat(drawer): add demo and api document for 'tipsProps' * fix(docs): optimize api type anchor * fix(build): optimize build:theme script * docs(timeline): api document optimization * docs(steps): api document optimization * fix(pull-refresh): solved the problem pull down can't reset data * fix(build:theme): solved running build:theme script error
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@@ -128,6 +128,7 @@ | |||
:key="anchorRefreshKey" | |||
mask-class="custom-active-anchor" | |||
@link-click="handleAnchorClick" | |||
class="anchor" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
这个新增的类名是没有用到么~
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
好像是,我改一下
* docs(sites): add deep style in scoped * docs(sites): add deep style in scoped
…Ww/tiny-vue into fix/site-sidebar-style
[e2e-test-warn] The title of the Pull request should look like "fix(vue-renderless): [action-menu, alert] fix xxx bug". Please make sure you've read our contributing guide |
PR
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: #1448
What is the new behavior?
Does this PR introduce a breaking change?
Other information