Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 295582

Summary:

[Widgets] READ_ONLY Text widget consumes mousewheel events

Product:

[Eclipse Project] Platform

Reporter:

Tim Moore <tmm-bugs.eclipse>

Component:

SWT

Assignee:

Platform-SWT-Inbox <platform-swt-inbox>

Status:

CLOSED WONTFIX

QA Contact:

Felipe Heidrich <eclipse.felipe>

Severity:

normal

Priority:

Keywords:

triaged

Version:

4.0

Target Milestone:

---

Hardware:

OS:

Windows 7

Whiteboard:

stalebug

Attachments:

Description	Flags
Interactive test case	none

Description Tim Moore

2009-11-19 07:48:44 EST

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.0.15) Gecko/2009102704 Fedora/3.0.15-1.fc10 Firefox/3.0.15
Build Identifier: I20090611-1540

If you embed a writable Text widget into a ScrolledComposite, mouseWheel events are propagated up to the ScrolledComposite correctly. However, if the Text widget is constructed with the SWT.READ_ONLY style, the events are not propagated.
Contrast this to StyledText, which propagates the events in both cases.

Reproducible: Always

Steps to Reproduce:
Run the interactive test that I will shortly attach.

Comment 1 Tim Moore

2009-11-19 07:53:09 EST

Created attachment 152574 [details]
Interactive test case

Comment 2 Felipe Heidrich

2009-11-19 15:11:45 EST

Similar to Bug 244664

Comment 3 Leo Ufimtsev

2017-08-03 12:32:57 EDT

This is a one-off bulk update. (The last one in the triage migration).

Moving bugs from swt-triaged@eclipse to platform-swt-inbox@eclipse.org and adding "triaged" keyword as per new triage process:
https://wiki.eclipse.org/SWT/Devel/Triage

See Bug 518478 for details.

Tag for notification/mail filters:
@TriageBulkUpdate

Comment 4 Eclipse Genie

2019-09-06 17:56:39 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.