<!-- 
RSS generated by JIRA (9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13) at Sun Jan 12 12:21:34 UTC 2025

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>Mojang Studios Jira</title>
    <link>https://bugs.mojang.com</link>
    <description>This file is an XML representation of an issue</description>
    <language>en</language>    <build-info>
        <version>9.12.2</version>
        <build-number>9120002</build-number>
        <build-date>10-01-2024</build-date>
    </build-info>


<item>
            <title>[MC-9582] Whole-word selection behaves erratically in chat</title>
                <link>https://bugs.mojang.com/browse/MC-9582</link>
                <project id="10400" key="MC">Minecraft: Java Edition</project>
                    <description>&lt;p&gt;Trying to select a word using ctrl+shift+left or ctrl+shift+right will work for one word only. It appears to attempt to match the selection starting from the wrong selection anchor.&lt;br/&gt;
Two otherwise extremely useful key combinations, &quot;home, shift+&lt;span class=&quot;error&quot;&gt;&amp;#91;end, ctrl+left&amp;#93;&lt;/span&gt;&quot; and &quot;end, shift+&lt;span class=&quot;error&quot;&gt;&amp;#91;home, ctrl+right&amp;#93;&lt;/span&gt;&quot; are both affected adversely by this.&lt;/p&gt;</description>
                <environment></environment>
        <key id="23210">MC-9582</key>
            <summary>Whole-word selection behaves erratically in chat</summary>
                <type id="1" iconUrl="https://bugs.mojang.com/secure/viewavatar?size=xsmall&amp;avatarId=18903&amp;avatarType=issuetype">Bug</type>
                                    <status id="5" iconUrl="https://bugs.mojang.com/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="1">Fixed</resolution>
                                        <assignee username="dinnerbone">[Mojang] Nathan Adams</assignee>
                                    <reporter username="score_under">score</reporter>
                        <labels>
                            <label>chat</label>
                            <label>input</label>
                            <label>textbox</label>
                    </labels>
                <created>Sun, 10 Feb 2013 21:39:12 +0100</created>
                <updated>Tue, 21 Jan 2014 15:48:57 +0100</updated>
                            <resolved>Tue, 21 Jan 2014 15:48:57 +0100</resolved>
                                    <version>Minecraft 1.4.7</version>
                    <version>Snapshot 13w06a</version>
                    <version>Minecraft 1.5</version>
                    <version>Snapshot 13w11a</version>
                    <version>Minecraft 1.7.4</version>
                                    <fixVersion>Minecraft 14w04a</fixVersion>
                                                        <votes>2</votes>
                                    <watches>2</watches>
                                                                            <comments>
                            <comment id="133006" author="torabi" created="Mon, 20 Jan 2014 07:11:11 +0100"  >&lt;p&gt;Do you have any experience with obfuscation? The whole point is to mangle the code so that it&apos;s unrecognizable, and yet still functions. Compiler optimizations do much the same as a side-effect, with the actual goal being efficiency. So no, the structure of the code isn&apos;t necessarily all that similar. Dinnerbone &lt;a href=&quot;https://twitter.com/Dinnerbone/status/394863850715369472&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;has said&lt;/a&gt; that it&apos;s often more work to understand someone else&apos;s fix against the MCP codebase than to just fix it themselves. It&apos;s true that this is a very simple bug, and that your code snippet shows that, but it&apos;s really not relevant to it actually getting fixed. They have bigger fish to fry. Just because you (and me!) care about this doesn&apos;t make it important. Most people are not all that devoted to bug-free code (See &quot;worse is better&quot;). Once again, I&apos;m surprised this didn&apos;t get fixed in the big code review, as something like an unused parameter search would be an obvious thing to run, and would have highlighted this problem.&lt;/p&gt;</comment>
                            <comment id="132944" author="score_under" created="Mon, 20 Jan 2014 03:48:28 +0100"  >&lt;p&gt;Right, I&apos;m aware they do actually read reports, it&apos;s just generally frustrating that bugs like this go ignored for such long periods of time.&lt;/p&gt;

&lt;p&gt;As for the &quot;nothing like the actual source code&quot; claim, I&apos;m not so sure. I know it&apos;d be nothing like the source code visually, but when it comes to the structure it would be nearly the same, and recognisably so. Things like this broken delegation to another method would be almost exactly as they were in the original source code, but with some names changed. A good starting point would be to run IntelliJ&apos;s &quot;unused parameter&quot; inspection on classes handling textbox input, and assuming nothing out of the ordinary is going on here it would find the bug instantly (or rather, narrow it down to one of maybe 5 lines of code, from which it would be easy for a human to determine where the problem lies).&lt;/p&gt;
</comment>
                            <comment id="132936" author="torabi" created="Mon, 20 Jan 2014 02:31:39 +0100"  >&lt;p&gt;They do read bug reports, because the various developers occasionally comment, assign themselves to bugs, fix the bugs, and mark them fixed. However, there are &lt;a href=&quot;https://mojang.atlassian.net/issues/?filter=11703&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;over 2000 open reports&lt;/a&gt;, and &lt;a href=&quot;https://mojang.atlassian.net/issues/?filter=10620&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;over 40000 total reports&lt;/a&gt; on the tracker. Most of which are garbage, either because they&apos;re duplicates, incomprehensible, or not actually bugs. It&apos;s a lot of work to sift through it all looking for valid issues to address. And despite how many employees Mojang now has, very few of them are actively developing Minecraft. Something like 5, now that &lt;a href=&quot;https://bugs.mojang.com/secure/ViewProfile.jspa?name=TheMoogle&quot; class=&quot;user-hover&quot; rel=&quot;TheMoogle&quot;&gt;TheMoogle&lt;/a&gt; and &lt;a href=&quot;https://bugs.mojang.com/secure/ViewProfile.jspa?name=searge&quot; class=&quot;user-hover&quot; rel=&quot;searge&quot;&gt;searge&lt;/a&gt; have joined the team.&lt;/p&gt;

&lt;p&gt;The vote count also figures into putting priority on fixing bugs. This one is also obviously not an issue for many people, as there are only two votes (one of them&apos;s mine!), and zero duplicate reports. The thing is, no matter how quick and easy it would be to fix something, there&apos;s still hundreds, if not thousands, of other things all demanding the same time and attention. Fixing this would mean something else gets put off, even if it&apos;s only by 5 minutes. With so many people filing reports, some of them are bound to be put off, no matter how fast they work.&lt;/p&gt;

&lt;p&gt;Also consider that fixes based on decompiled code are useless to the Mojang developers, because &lt;a href=&quot;https://twitter.com/Dinnerbone/status/377920596589703168&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;it&apos;s nothing like the actual source code&lt;/a&gt;. I&apos;m kind of surprised this bug survived the big code review, however.&lt;/p&gt;</comment>
                            <comment id="132890" author="score_under" created="Sun, 19 Jan 2014 22:11:58 +0100"  >&lt;p&gt;Added the current version, just remembered to actually test it. This bug has been present since the inception of the new chat system around version 1.2.5 IIRC.&lt;/p&gt;

&lt;p&gt;If only Mojang read bug reports... it is frustrating to know exactly the mistake made and exactly how to fix it in less than ten keystrokes in the IDE, and to report where the problem is exactly in the code, only to have this ignored for just shy of a year. It&apos;s not a matter of not knowing the solution, it&apos;s a matter of simply not reading this report.&lt;/p&gt;</comment>
                            <comment id="128536" author="bljat" created="Wed, 1 Jan 2014 00:28:10 +0100"  >&lt;p&gt;Is this still a concern in the &lt;em&gt;current Minecraft version&lt;/em&gt; &lt;b&gt;1.7.4&lt;/b&gt; / Launcher version &lt;b&gt;1.3.7&lt;/b&gt; or later? If so, please &lt;em&gt;update the affected versions&lt;/em&gt; in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.&lt;/p&gt;</comment>
                            <comment id="55559" author="score_under" created="Tue, 19 Mar 2013 21:00:30 +0100"  >&lt;p&gt;Just so that it&apos;s 100% obvious exactly where the bug is and why it happens (added a picture)&lt;/p&gt;</comment>
                            <comment id="55241" author="kumasasa" created="Mon, 18 Mar 2013 23:07:43 +0100"  >&lt;p&gt;Confirmed in 1.5&lt;/p&gt;</comment>
                            <comment id="52101" author="score_under" created="Tue, 12 Mar 2013 19:20:16 +0100"  >&lt;p&gt;For the record (and for mojang): in the textbox class, the (overloaded) function used to find a word given a position and offset... ignores the offset. Looks like a copy/paste gone wrong.&lt;/p&gt;</comment>
                            <comment id="45218" author="kumasasa" created="Mon, 11 Feb 2013 09:07:59 +0100"  >&lt;p&gt;Confirmed (Windows 7)&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                            <attachment id="25520" name="extra super clear.png" size="23387" author="score_under" created="Tue, 19 Mar 2013 21:00:30 +0100"/>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                <customfield id="customfield_10701" key="com.atlassian.jira.plugin.system.customfieldtypes:datetime">
                        <customfieldname>CHK</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Mon, 11 Feb 2013 09:07:00 +0100</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10500" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Confirmation Status</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10303"><![CDATA[Confirmed]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_11700" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_11600" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i0ao2n:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                    </customfields>
    </item>
</channel>
</rss>