github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-05-21 20:35:31 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Fomantic: Transition: Element is no longer attached to DOM #5017

New Issue
Closed
opened 2025-11-02 06:11:02 -06:00 by GiteaMirror · 7 comments
GiteaMirror commented 2025-11-02 06:11:02 -06:00
Owner
Copy Link

Originally created by @silverwind on GitHub (Mar 7, 2020).

This is apparently still happening rarely, opening this issue to track it further.

I don't know the exact cause but when it happens, semantic.min.css is missing some CSS rules which in turn breaks a lot of functionality in the UI. More investigation on what exactly is not being built is needed. I suspect a underlying race condition in Fomantic's build process.

Workaround is just to rebuild fomantic (make fomantic) until it produces proper files.

Originally created by @silverwind on GitHub (Mar 7, 2020). This is apparently still happening rarely, opening this issue to track it further. I don't know the exact cause but when it happens, `semantic.min.css` is missing some CSS rules which in turn breaks a lot of functionality in the UI. More investigation on what exactly is not being built is needed. I suspect a underlying race condition in Fomantic's build process. Workaround is just to rebuild fomantic (`make fomantic`) until it produces proper files.
GiteaMirror added the topic/uitype/bug labels 2025-11-02 06:11:02 -06:00
GiteaMirror commented 2025-11-02 06:11:03 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Mar 7, 2020):

Thanks for looking into this @silverwind

@zeripath commented on GitHub (Mar 7, 2020): Thanks for looking into this @silverwind
GiteaMirror commented 2025-11-02 06:11:03 -06:00
Author
Owner
Copy Link

@silverwind commented on GitHub (Mar 7, 2020):

I reproduced within 6 build cycles:

705K public/fomantic/semantic.min.css
705K public/fomantic/semantic.min.css
705K public/fomantic/semantic.min.css
705K public/fomantic/semantic.min.css
673K public/fomantic/semantic.min.css
705K public/fomantic/semantic.min.css

Checking if I can reproduce in the Fomantic repo itself.

@silverwind commented on GitHub (Mar 7, 2020): I reproduced within 6 build cycles: ```` 705K public/fomantic/semantic.min.css 705K public/fomantic/semantic.min.css 705K public/fomantic/semantic.min.css 705K public/fomantic/semantic.min.css 673K public/fomantic/semantic.min.css 705K public/fomantic/semantic.min.css ```` Checking if I can reproduce in the Fomantic repo itself.
GiteaMirror commented 2025-11-02 06:11:03 -06:00
Author
Owner
Copy Link

@silverwind commented on GitHub (Mar 7, 2020):

Also reproducible in the Fomantic repo:

$ while true; do rm -rf dist && npx gulp build &>/dev/null && stat --printf="%s" dist/semantic.min.css | xargs; done
1354924
1354924
1321417
1354924
1354924
1321417
1321417

Bug report coming up soon.

@silverwind commented on GitHub (Mar 7, 2020): Also reproducible in the Fomantic repo: ```` $ while true; do rm -rf dist && npx gulp build &>/dev/null && stat --printf="%s" dist/semantic.min.css | xargs; done 1354924 1354924 1321417 1354924 1354924 1321417 1321417 ```` Bug report coming up soon.
GiteaMirror commented 2025-11-02 06:11:03 -06:00
Author
Owner
Copy Link

@silverwind commented on GitHub (Mar 7, 2020):

https://github.com/fomantic/Fomantic-UI/issues/1356

@silverwind commented on GitHub (Mar 7, 2020): https://github.com/fomantic/Fomantic-UI/issues/1356
GiteaMirror commented 2025-11-02 06:11:04 -06:00
Author
Owner
Copy Link

@kaptinlin commented on GitHub (Mar 7, 2020):

I have this issue too after install gitea.

Transition: Element is no longer attached to DOM. Unable to animate.  Use silent setting to surpress this warning in production. slide down in <div class=​"menu" tabindex=​"-1">​…​</div>​
error @ semantic.min.js?v=f820ffd1cde10fabc3a8915a0e5b6b1e:11
animate @ semantic.min.js?v=f820ffd1cde10fabc3a8915a0e5b6b1e:11
initialize @ semantic.min.js?v=f820ffd1cde10fabc3a8915a0e5b6b1e:11
(anonymous) @ semantic.min.js?v=f820ffd1cde10fabc3a8915a0e5b6b1e:11
each @ jquery.js?v=f820ffd1cde10fabc3a8915a0e5b6b1e:1
each @ jquery.js?v=f820ffd1cde10fabc3a8915a0e5b6b1e:1
(anonymous) @ semantic.min.js?v=f820ffd1cde10fabc3a8915a0e5b6b1e:11
show @ semanticDropdown.js:3641
show @ semanticDropdown.js:603
toggle @ semanticDropdown.js:576
eventOnElement @ semanticDropdown.js:1799
toggle @ semanticDropdown.js:1287
dispatch @ jquery.js?v=f820ffd1cde10fabc3a8915a0e5b6b1e:1
(anonymous) @ jquery.js?v=f820ffd1cde10fabc3a8915a0e5b6b1e:1
@kaptinlin commented on GitHub (Mar 7, 2020): I have this issue too after install gitea. ``` Transition: Element is no longer attached to DOM. Unable to animate. Use silent setting to surpress this warning in production. slide down in <div class=​"menu" tabindex=​"-1">​…​</div>​ error @ semantic.min.js?v=f820ffd1cde10fabc3a8915a0e5b6b1e:11 animate @ semantic.min.js?v=f820ffd1cde10fabc3a8915a0e5b6b1e:11 initialize @ semantic.min.js?v=f820ffd1cde10fabc3a8915a0e5b6b1e:11 (anonymous) @ semantic.min.js?v=f820ffd1cde10fabc3a8915a0e5b6b1e:11 each @ jquery.js?v=f820ffd1cde10fabc3a8915a0e5b6b1e:1 each @ jquery.js?v=f820ffd1cde10fabc3a8915a0e5b6b1e:1 (anonymous) @ semantic.min.js?v=f820ffd1cde10fabc3a8915a0e5b6b1e:11 show @ semanticDropdown.js:3641 show @ semanticDropdown.js:603 toggle @ semanticDropdown.js:576 eventOnElement @ semanticDropdown.js:1799 toggle @ semanticDropdown.js:1287 dispatch @ jquery.js?v=f820ffd1cde10fabc3a8915a0e5b6b1e:1 (anonymous) @ jquery.js?v=f820ffd1cde10fabc3a8915a0e5b6b1e:1 ```
GiteaMirror commented 2025-11-02 06:11:04 -06:00
Author
Owner
Copy Link

@silverwind commented on GitHub (Mar 7, 2020):

@KaptinLin should be resolved in the lastest master build.

@silverwind commented on GitHub (Mar 7, 2020): @KaptinLin should be resolved in the lastest master build.
GiteaMirror commented 2025-11-02 06:11:04 -06:00
Author
Owner
Copy Link

@silverwind commented on GitHub (Apr 10, 2020):

Closing, workaround (https://github.com/go-gitea/gitea/pull/10655) will be removed next Fomantic release.

@silverwind commented on GitHub (Apr 10, 2020): Closing, workaround (https://github.com/go-gitea/gitea/pull/10655) will be removed next Fomantic release.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label topic/ui type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#5017
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?