Bug 134311 - Data validity fails when pasting into cell
Summary: Data validity fails when pasting into cell
Status: RESOLVED DUPLICATE of bug 115081
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.4.4.2 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-06-25 22:10 UTC by Nick_K
Modified: 2020-12-15 10:27 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nick_K 2020-06-25 22:10:15 UTC
Description:
I have a data validity rule set that works when entering data from the keyboard.  It verifies { <0 OR "Void" }(less the {}). so -23 or Void is an OK entry. 0, 12 or any other text fails.

The Bug: When I copied the number 4 from a webpage (or a LO word document) and pasted (ctrl V) it into the cell the data validity rule failed to block the entry.

Steps to Reproduce:
1.Create this data validity per ... OR(G28<0, G28="VOID")
2.Goto https://bikepacking.com/gear/rivnut-bottle-cage-mounts/
3.Goto the text: 4. INSTALL THE RIVNUT
4. Copy the "4" and past into the data validated cell

Actual Results:
Allows number to be entered when it should have blocked it

Expected Results:
Thrown the message that was created when the data validity failed.


Reproducible: Always


User Profile Reset: No



Additional Info:
I copied a number from a LO Document and it allowed pasting as did the text from the webpage. The cell that failed using the paste did work before and after the paste when typing the value.
Comment 1 sora34ce 2020-09-10 17:09:30 UTC
As far as I tested, the error doesn't work in my version

Version: 7.1.0.0.alpha0+
Build ID: 52820b52b3bca45e2db527d1cc5f4488b2e0b9d0
CPU threads: 8; OS: Mac OS X 10.15.6; UI render: default; VCL: osx
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded
Comment 2 Justin L 2020-12-15 10:27:27 UTC

*** This bug has been marked as a duplicate of bug 115081 ***