Bug 271181 - [Plasma/JavaScript/API] 'switch' expression works wrong with value from a readConfig call
Summary: [Plasma/JavaScript/API] 'switch' expression works wrong with value from a rea...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: plasma4
Classification: Plasma
Component: scriptengines (show other bugs)
Version: 4.8.3
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-17 21:04 UTC by Nikita Melnichenko
Modified: 2018-06-08 19:43 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
The example plasmoid that reproduces the bug. (1.85 KB, application/octet-stream)
2011-04-17 21:04 UTC, Nikita Melnichenko
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nikita Melnichenko 2011-04-17 21:04:19 UTC
Created attachment 59074 [details]
The example plasmoid that reproduces the bug.

Version:           unspecified (using KDE 4.6.2) 
OS:                Linux

I use plasmoid.readConfig to read a value to do a certain action depending on that value. My plasmoid contains language construct
switch (value)
{
...
}
that doesn't work as expected.

Reproducible: Always

Steps to Reproduce:
Run the example plasmoid.
Comment 1 Myriam Schweingruber 2012-05-27 11:19:13 UTC
Is this still valid for KDE 4.8.3 or trunk?
Comment 2 Nikita Melnichenko 2012-06-13 18:43:14 UTC
Yes, this bug is still valid for 4.8.3. Check out my testcase, please!!!
Comment 3 Nate Graham 2018-06-08 19:43:03 UTC
Hello!

This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug is already resolved in Plasma 5.

Accordingly, we hope you understand why we must close this bug report. If the issue described  here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting

If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging

Thanks for your understanding!

Nate Graham