-
Notifications
You must be signed in to change notification settings - Fork 36
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] Selection: Loop selection based on content #3573
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Similarly to the issue addressed in PR #3214, we want `loopSelection` to consider seemingly empty cells when considering the expansion zone. This revision splits the behaviour of the selection processor for `loopSelection` and the other navigation features (like cluster jumping) as we still want to ignore cells with an empty evaluation in those cases. The reason being that the user could be lost if, when navigating with their keyboards, they end up with their selection on empty cell. As for #3214, the fix will need to be adapted to account for the spreaded formulas. Task: 3709340
rrahir
force-pushed
the
saas-16.1-emptycell-not-cellvalue-rar
branch
from
January 30, 2024 18:25
ce0f61d
to
c03cbf2
Compare
@fw-bot up to saas-16.3 |
Forward-porting to 'saas-16.3'. |
rrahir
added a commit
that referenced
this pull request
Jan 31, 2024
Similarly to the issue addressed in PR #3214, we want `loopSelection` to consider seemingly empty cells when considering the expansion zone. This revision splits the behaviour of the selection processor for `loopSelection` and the other navigation features (like cluster jumping) as we still want to ignore cells with an empty evaluation in those cases. The reason being that the user could be lost if, when navigating with their keyboards, they end up with their selection on empty cell. This PR is the adaptation of #3573 to support cells that contain the result of a spreaded formula. Task: 3709340
14 tasks
LucasLefevre
approved these changes
Feb 9, 2024
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.
robodoo r+
robodoo
pushed a commit
that referenced
this pull request
Feb 9, 2024
Similarly to the issue addressed in PR #3214, we want `loopSelection` to consider seemingly empty cells when considering the expansion zone. This revision splits the behaviour of the selection processor for `loopSelection` and the other navigation features (like cluster jumping) as we still want to ignore cells with an empty evaluation in those cases. The reason being that the user could be lost if, when navigating with their keyboards, they end up with their selection on empty cell. As for #3214, the fix will need to be adapted to account for the spreaded formulas. closes #3573 Task: 3709340 Signed-off-by: Lucas Lefèvre (lul) <lul@odoo.com>
robodoo
pushed a commit
that referenced
this pull request
Feb 9, 2024
Similarly to the issue addressed in PR #3214, we want `loopSelection` to consider seemingly empty cells when considering the expansion zone. This revision splits the behaviour of the selection processor for `loopSelection` and the other navigation features (like cluster jumping) as we still want to ignore cells with an empty evaluation in those cases. The reason being that the user could be lost if, when navigating with their keyboards, they end up with their selection on empty cell. This PR is the adaptation of #3573 to support cells that contain the result of a spreaded formula. closes #3577 Task: 3709340 Signed-off-by: Lucas Lefèvre (lul) <lul@odoo.com>
14 tasks
fw-bot
pushed a commit
that referenced
this pull request
Feb 9, 2024
Similarly to the issue addressed in PR #3214, we want `loopSelection` to consider seemingly empty cells when considering the expansion zone. This revision splits the behaviour of the selection processor for `loopSelection` and the other navigation features (like cluster jumping) as we still want to ignore cells with an empty evaluation in those cases. The reason being that the user could be lost if, when navigating with their keyboards, they end up with their selection on empty cell. This PR is the adaptation of #3573 to support cells that contain the result of a spreaded formula. Task: 3709340 X-original-commit: 2e69e1b
14 tasks
14 tasks
robodoo
pushed a commit
that referenced
this pull request
Feb 9, 2024
Similarly to the issue addressed in PR #3214, we want `loopSelection` to consider seemingly empty cells when considering the expansion zone. This revision splits the behaviour of the selection processor for `loopSelection` and the other navigation features (like cluster jumping) as we still want to ignore cells with an empty evaluation in those cases. The reason being that the user could be lost if, when navigating with their keyboards, they end up with their selection on empty cell. This PR is the adaptation of #3573 to support cells that contain the result of a spreaded formula. closes #3664 Task: 3709340 X-original-commit: 2e69e1b Signed-off-by: Lucas Lefèvre (lul) <lul@odoo.com> Signed-off-by: Rémi Rahir (rar) <rar@odoo.com>
14 tasks
rrahir
added a commit
that referenced
this pull request
Feb 10, 2024
Similarly to the issue addressed in PR #3214, we want `loopSelection` to consider seemingly empty cells when considering the expansion zone. This revision splits the behaviour of the selection processor for `loopSelection` and the other navigation features (like cluster jumping) as we still want to ignore cells with an empty evaluation in those cases. The reason being that the user could be lost if, when navigating with their keyboards, they end up with their selection on empty cell. This PR is the adaptation of #3573 to support cells that contain the result of a spreaded formula. Task: 3709340 X-original-commit: 2e69e1b
robodoo
pushed a commit
that referenced
this pull request
Feb 10, 2024
Similarly to the issue addressed in PR #3214, we want `loopSelection` to consider seemingly empty cells when considering the expansion zone. This revision splits the behaviour of the selection processor for `loopSelection` and the other navigation features (like cluster jumping) as we still want to ignore cells with an empty evaluation in those cases. The reason being that the user could be lost if, when navigating with their keyboards, they end up with their selection on empty cell. This PR is the adaptation of #3573 to support cells that contain the result of a spreaded formula. closes #3665 Task: 3709340 X-original-commit: 2e69e1b Signed-off-by: Lucas Lefèvre (lul) <lul@odoo.com> Signed-off-by: Rémi Rahir (rar) <rar@odoo.com>
14 tasks
rrahir
added a commit
that referenced
this pull request
Feb 12, 2024
Similarly to the issue addressed in PR #3214, we want `loopSelection` to consider seemingly empty cells when considering the expansion zone. This revision splits the behaviour of the selection processor for `loopSelection` and the other navigation features (like cluster jumping) as we still want to ignore cells with an empty evaluation in those cases. The reason being that the user could be lost if, when navigating with their keyboards, they end up with their selection on empty cell. This PR is the adaptation of #3573 to support cells that contain the result of a spreaded formula. Task: 3709340 X-original-commit: 4ad2b93
robodoo
pushed a commit
that referenced
this pull request
Feb 12, 2024
Similarly to the issue addressed in PR #3214, we want `loopSelection` to consider seemingly empty cells when considering the expansion zone. This revision splits the behaviour of the selection processor for `loopSelection` and the other navigation features (like cluster jumping) as we still want to ignore cells with an empty evaluation in those cases. The reason being that the user could be lost if, when navigating with their keyboards, they end up with their selection on empty cell. This PR is the adaptation of #3573 to support cells that contain the result of a spreaded formula. closes #3668 Task: 3709340 X-original-commit: 4ad2b93 Signed-off-by: Lucas Lefèvre (lul) <lul@odoo.com> Signed-off-by: Rémi Rahir (rar) <rar@odoo.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Similarly to the issue addressed in PR #3214, we want
loopSelection
to consider seemingly empty cells when considering the expansion zone.This revision splits the behaviour of the selection processor for
loopSelection
and the other navigation features (like cluster jumping) as we still want to ignore cells with an empty evaluation in those cases. The reason being that the user could be lost if, when navigating with their keyboards, they end up with their selection on empty cell.As for #3214, the fix will need to be adapted to account for the spreaded formulas.
Task: 3709340
Description:
description of this task, what is implemented and why it is implemented that way.
Task: : TASK_ID
review checklist