Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Refactor legacy line-number and scroll code#33094

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
wxiaoguang merged 5 commits intogo-gitea:mainfromwxiaoguang:refactor-line-scroll
Jan 4, 2025

Conversation

@wxiaoguang
Copy link
Contributor

@wxiaoguangwxiaoguang commentedJan 3, 2025
edited
Loading

  1. remove jquery
  2. rewrite the "line number selection", fix various edge cases
  3. fix the scroll

Now 7 "import jquery" files left.

Some fixes could be backport to 1.23 (not blocking the release)

image

image

image

@GiteaBotGiteaBot added the lgtm/need 2This PR needs two approvals by maintainers to be considered for merging. labelJan 3, 2025
@GiteaBotGiteaBot added lgtm/need 1This PR needs approval from one additional maintainer to be merged. and removed lgtm/need 2This PR needs two approvals by maintainers to be considered for merging. labelsJan 3, 2025

.ui.dropdown .menu> .header {
font-size:0.8em;
text-transform: none;/* reset fomantic's "uppercase" */
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

do we really want this?

image

Copy link
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Sure, we have fixed all "uppercase" headers in history, modern UI doesn't use uppercase.

This is the last one.

Copy link
ContributorAuthor

@wxiaoguangwxiaoguangJan 4, 2025
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

ps: many languages do not have "uppercase".

Fine tuned the font size:31e9deb

Details

image

metiftikci reacted with thumbs up emoji
// set scrollRestoration to 'manual' when there is a hash in url, so that the scroll position will not be remembered after refreshing
if(window.history.scrollRestoration!=='manual')window.history.scrollRestoration='manual';
// wait for a while because some elements (eg: image, editor, etc.) may change the viewport's height.
setTimeout(()=>commentDiv.scrollIntoView({block:'start'}),100);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

maybe center better?

Copy link
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

I have tested, "center" is not good enough. For example, when the comment is quite long.

}
};
onHashChange();
window.addEventListener('hashchange',onHashChange);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

just to inform,history.pushState does not fire hashchange event, so not sure if this listener does something

Copy link
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

It is the case when user manually change the URL, eg:

/file#L1 =>/file#L1-L3

And that's the old logic, I think it is good to keep it

if(first){
// set scrollRestoration to 'manual' when there is a hash in url, so that the scroll position will not be remembered after refreshing
if(window.history.scrollRestoration!=='manual')window.history.scrollRestoration='manual';
first.scrollIntoView({block:'start'});
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

same here. maybe center better?

Copy link
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

According to my test, I think "start" is better.

@GiteaBotGiteaBot added lgtm/doneThis PR has enough approvals to get merged. There are no important open reservations anymore. and removed lgtm/need 1This PR needs approval from one additional maintainer to be merged. labelsJan 3, 2025
lafriks pushed a commit that referenced this pull requestJan 3, 2025
Partially backport#33094 Fix the scroll bug in issue/pr view page.Fix a JS error when line number exceeds the max
@wxiaoguangwxiaoguang merged commit2b064b8 intogo-gitea:mainJan 4, 2025
26 checks passed
@GiteaBotGiteaBot added this to the1.24.0 milestoneJan 4, 2025
@wxiaoguangwxiaoguang deleted the refactor-line-scroll branchJanuary 4, 2025 02:56
zjjhot added a commit to zjjhot/gitea that referenced this pull requestJan 6, 2025
* giteaofficial/main:  [skip ci] Updated translations via Crowdin  Fix dropdown menu header and mobile view (go-gitea#33108)  workflow_dispatch use workflow from trigger branch (go-gitea#33098)  [skip ci] Updated translations via Crowdin  Trivial fixes (go-gitea#33103)  Fix empty git repo handling logic (go-gitea#33101)  Refactor legacy line-number and scroll code (go-gitea#33094)  Use `Project-URL` metadata field to get a PyPI package's homepage URL (go-gitea#33089)  Clean up legacy form CSS styles (go-gitea#33081)  [skip ci] Updated translations via Crowdin  add myself to maintainers (go-gitea#33088)  Make Gitea always use its internal config, ignore `/etc/gitconfig` (go-gitea#33076)  Fix "stop time tracking button" on navbar (go-gitea#33084)  Fix bleve fuzziness search (go-gitea#33078)  Try to fix ACME directory problem (go-gitea#33072)  Refactor env var related code (go-gitea#33075)
@go-giteago-gitea locked asresolvedand limited conversation to collaboratorsApr 4, 2025
Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.

Reviewers

@delvhdelvhdelvh approved these changes

@lunnylunnylunny approved these changes

+1 more reviewer

@metiftikcimetiftikcimetiftikci left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

lgtm/doneThis PR has enough approvals to get merged. There are no important open reservations anymore.modifies/frontend

Projects

None yet

Milestone

1.24.0

Development

Successfully merging this pull request may close these issues.

5 participants

@wxiaoguang@lunny@metiftikci@delvh@GiteaBot

[8]ページ先頭

©2009-2025 Movatter.jp