<?xml version="1.0" encoding="utf-8" ?>
<?xml-stylesheet type="text/xsl" href="RSS_xslt_style.asp" version="1.0" ?>
<rss version="2.0" xmlns:WebWizForums="https://syndication.webwiz.net/rss_namespace/">
 <channel>
  <title>Codejock Developer Community</title>
  <link>http://forum.codejock.com/</link>
  <description><![CDATA[This is an XML content feed of; Codejock Developer Community : Last 10 Posts]]></description>
  <copyright>Copyright (c) 2006-2013 Web Wiz Forums - All Rights Reserved.</copyright>
  <pubDate>Mon, 19 Oct 2026 13:32:43 +0000</pubDate>
  <lastBuildDate>Tue, 15 Sep 2026 03:27:00 +0000</lastBuildDate>
  <docs>http://blogs.law.harvard.edu/tech/rss</docs>
  <generator>Web Wiz Forums 12.04</generator>
  <ttl>30</ttl>
  <WebWizForums:feedURL>forum.codejock.com/RSS_topic_feed.asp</WebWizForums:feedURL>
  <image>
   <title><![CDATA[Codejock Developer Community]]></title>
   <url>http://forum.codejock.com/forum_images/codejock-logo.gif</url>
   <link>http://forum.codejock.com/</link>
  </image>
  <item>
   <title><![CDATA[Toolkit Pro : Visual Studio 2026]]></title>
   <link>http://forum.codejock.com/forum_posts.asp?TID=24636&amp;PID=79476&amp;title=visual-studio-2026#79476</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="http://forum.codejock.com/member_profile.asp?PF=451">Heath</a><br /><strong>Subject:</strong> Visual Studio 2026<br /><strong>Posted:</strong> 15 September 2026 at 3:27am<br /><br />VS 2026 has been out 10 months. As I've said before, I think Codejock should prioritise VS version support over major new features.&nbsp;<div><br></div><div>A 23.4.1 release with just the VS 2026 would perfect whilst the next mega vNext trundles on.</div><div><br></div><div>Currently I'm having to maintain and patch VS 2022 and 2026.</div>]]>
   </description>
   <pubDate>Tue, 15 Sep 2026 03:27:00 +0000</pubDate>
   <guid isPermaLink="true">http://forum.codejock.com/forum_posts.asp?TID=24636&amp;PID=79476&amp;title=visual-studio-2026#79476</guid>
  </item> 
  <item>
   <title><![CDATA[Toolkit Pro : Visual Studio 2026]]></title>
   <link>http://forum.codejock.com/forum_posts.asp?TID=24636&amp;PID=79475&amp;title=visual-studio-2026#79475</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="http://forum.codejock.com/member_profile.asp?PF=8916">angelsoriasanagustin</a><br /><strong>Subject:</strong> Visual Studio 2026<br /><strong>Posted:</strong> 14 September 2026 at 6:47am<br /><br />Release date ?, please....]]>
   </description>
   <pubDate>Mon, 14 Sep 2026 06:47:02 +0000</pubDate>
   <guid isPermaLink="true">http://forum.codejock.com/forum_posts.asp?TID=24636&amp;PID=79475&amp;title=visual-studio-2026#79475</guid>
  </item> 
  <item>
   <title><![CDATA[Skin Framework : Context menu tracking when Skinning]]></title>
   <link>http://forum.codejock.com/forum_posts.asp?TID=24694&amp;PID=79473&amp;title=context-menu-tracking-when-skinning#79473</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="http://forum.codejock.com/member_profile.asp?PF=3213">rdhd</a><br /><strong>Subject:</strong> Context menu tracking when Skinning<br /><strong>Posted:</strong> 01 September 2026 at 1:33pm<br /><br /><div>Mea cupla. It wasn't skinning that caused the dismissal. It was the fact that I had to use CJ TrackPopupMenu to get the skin applied to the context menu. We have the code here being used in cases where we don't have a popup displaying the item for which we are showing the context menu.</div><div><br></div><div>So I guess the work-around I have though seemingly a bit dangerous (subject to CJ changes over time ...) is probably the best I can do.</div>]]>
   </description>
   <pubDate>Tue, 01 Sep 2026 13:33:35 +0000</pubDate>
   <guid isPermaLink="true">http://forum.codejock.com/forum_posts.asp?TID=24694&amp;PID=79473&amp;title=context-menu-tracking-when-skinning#79473</guid>
  </item> 
  <item>
   <title><![CDATA[Skin Framework : Context menu tracking when Skinning]]></title>
   <link>http://forum.codejock.com/forum_posts.asp?TID=24694&amp;PID=79472&amp;title=context-menu-tracking-when-skinning#79472</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="http://forum.codejock.com/member_profile.asp?PF=3213">rdhd</a><br /><strong>Subject:</strong> Context menu tracking when Skinning<br /><strong>Posted:</strong> 01 September 2026 at 1:18pm<br /><br /><div>I found that when I have a skin applied and I do a right click on a control on some of our popups the context menu I track causes the popup to dismiss. To fix that I found I could pass in TPM_RECURSE when tracking the popup menu. That keeps CJ from closing the popup. Unfortunately it also lets CJ track the mouse wrt the popup as well as the context menu (popup itself). Well sort of. The context menu items don't highlight as I move over them though the items on the popup below it do. When I click a context menu item I do get the command ID back.</div><div><br></div><div>Not a fan of my work-around which is described and implemented as:</div><div><br></div><div><pre style="font-family:'Cascadia Mono';font-size:9pt;color:#000000">            <span style="color:#008000">// 12/22/25: RDH PR 11388058. This code was changed to call the frame window so the menu displays a Dark</span>            <span style="color:#008000">// theme. That api routes through Codejock's CXTPCommandBars::TrackPopupMenu, which calls</span>            <span style="color:#008000">// XTPMouseManager::SendTrackLost on entry. SendTrackLost walks CXTPMouseManager::m_arrTracked calling</span>            <span style="color:#008000">// OnTrackLost, which ends tracking mode on the MRUPopupBar and closes the vertical MRU out from under us.</span>            <span style="color:#008000">//</span>            <span style="color:#008000">// 8/31/26 RDH: That was originally worked around by passing TPM_RECURSE, because Codejock skips</span>            <span style="color:#008000">// SendTrackLost when that flag is set. But TPM_RECURSE does not mean "leave my popup alone" - it also</span>            <span style="color:#008000">// calls LockTrackRecurse(TRUE), which bumps m_nLockRecurse on EVERY bar already being tracked, and</span>            <span style="color:#008000">// m_nLockRecurse is the flag that gates all hot tracking (CXTPPopupBar::OnMouseMove,</span>            <span style="color:#008000">// CXTPCommandBar::OnMouseMove and OnMouseLeave, the hover timers, CXTPMouseManager::DeliverMessage).</span>            <span style="color:#008000">// The result was a context menu whose items never highlighted, and stale highlights left lit on the MRU</span>            <span style="color:#008000">// items underneath because nothing was allowed to clear them.</span>            <span style="color:#008000">//</span>            <span style="color:#008000">// Removing just our own bar from the tracked array is not enough, and it is worth knowing why. An</span>            <span style="color:#008000">// MRUPopupBar is a CXTPRibbonSystemPopupBarPage, that is, a page of the system menu popup that spawned</span>            <span style="color:#008000">// it, and that parent bar is tracked too. SendTrackLost calls OnTrackLost on the parent, the parent</span>            <span style="color:#008000">// closes its child popups, and ours goes down with it however carefully we detached it. That is exactly</span>            <span style="color:#008000">// what TPM_RECURSE was papering over by locking the whole array rather than one entry.</span>            <span style="color:#008000">//</span>            <span style="color:#008000">// So do what TPM_RECURSE did, minus the freeze: lift the entire tracked array out for the duration of</span>            <span style="color:#008000">// the call and put it back afterwards. SendTrackLost then has nothing to walk and is a no op, every</span>            <span style="color:#008000">// bar keeps its tracking mode, and because nobody gets m_nLockRecurse set the context menu hot tracks</span>            <span style="color:#008000">// normally. The bars are restored in their original order, since SetTrack appends.</span>            <span style="color:#008000">//</span>            <span style="color:#008000">//</span>            <span style="color:#008000">// Do not try to solve this by vetoing dismissal in MRUPopupBar::SetTrackingMode instead. SendTrackLost</span>            <span style="color:#008000">// is "while (m_arrTracked.GetSize() &gt; 0) m_arrTracked&#091;0&#093;-&gt;OnTrackLost();" - a veto that stops a bar</span>            <span style="color:#008000">// being removed from the array hangs the thread.</span>            <span style="color:#2b91af">CXTPCommandBar</span>*   pOwningBar     = <span style="color:#6f008a">DYNAMIC_DOWNCAST</span><span style="color:#1a94ff">(</span><span style="color:#2b91af">MRUPopupBar</span>, GetParent<span style="color:#ffd702">()</span><span style="color:#1a94ff">)</span>;            <span style="color:#2b91af">CXTPMouseManager</span>* pMouseManager  = XTPMouseManager<span style="color:#1a94ff">()</span>;            std::<span style="color:#2b91af">vector</span>&lt;<span style="color:#2b91af">CXTPCommandBar</span>*&gt; vecSuspendedBars;            <span style="color:#0000ff">if</span><span style="color:#1a94ff">(</span>pOwningBar &amp;&amp; pMouseManager<span style="color:#1a94ff">)</span>            <span style="color:#1a94ff">{</span>                <span style="color:#2b91af">CXTPMouseManager</span>::<span style="color:#2b91af">CTrackArray</span>&amp; arrTracked = pMouseManager-&gt;GetTrackArray<span style="color:#ffd702">()</span>;                <span style="color:#0000ff">for</span><span style="color:#ffd702">(</span><span style="color:#0000ff">int</span> i = 0; i &lt; <span style="color:#d86ac2">(</span><span style="color:#0000ff">int</span><span style="color:#d86ac2">)</span>arrTracked.GetSize<span style="color:#d86ac2">()</span>; i++<span style="color:#ffd702">)</span>                <span style="color:#ffd702">{</span>                    vecSuspendedBars.push_back<span style="color:#d86ac2">(</span>arrTracked<span style="color:#008080">&#091;</span>i<span style="color:#008080">&#093;</span><span style="color:#d86ac2">)</span>;                <span style="color:#ffd702">}</span>                <span style="color:#0000ff">for</span><span style="color:#ffd702">(</span><span style="color:#2b91af">size_t</span> i = 0; i &lt; vecSuspendedBars.size<span style="color:#d86ac2">()</span>; i++<span style="color:#ffd702">)</span>                <span style="color:#ffd702">{</span>                    pMouseManager-&gt;RemoveTrack<span style="color:#d86ac2">(</span>vecSuspendedBars<span style="color:#008080">&#091;</span>i<span style="color:#008080">&#093;</span><span style="color:#d86ac2">)</span>;                <span style="color:#ffd702">}</span>            <span style="color:#1a94ff">}</span>            <span style="color:#2b91af">BOOL</span> item = pFrameWnd-&gt;TrackPopupMenu<span style="color:#1a94ff">(</span>subMenu, <span style="color:#6f008a">TPM_RETURNCMD</span> | <span style="color:#6f008a">TPM_LEFTALIGN</span> | <span style="color:#6f008a">TPM_LEFTBUTTON</span>, point.x, point.y, <span style="color:#0000ff">this</span>, <span style="color:#0000ff">nullptr</span>, <span style="color:#2f4f4f">JNone</span>, hInstance<span style="color:#1a94ff">)</span>;            <span style="color:#0000ff">for</span><span style="color:#1a94ff">(</span><span style="color:#2b91af">size_t</span> i = 0; i &lt; vecSuspendedBars.size<span style="color:#ffd702">()</span>; i++<span style="color:#1a94ff">)</span>            <span style="color:#1a94ff">{</span>                <span style="color:#008000">// The window can be gone if a command tore the bar down while the menu was up.</span>                <span style="color:#0000ff">if</span><span style="color:#ffd702">(</span>::IsWindow<span style="color:#d86ac2">(</span>vecSuspendedBars<span style="color:#008080">&#091;</span>i<span style="color:#008080">&#093;</span>-&gt;GetSafeHwnd<span style="color:#1a94ff">()</span><span style="color:#d86ac2">)</span><span style="color:#ffd702">)</span>                <span style="color:#ffd702">{</span>                    pMouseManager-&gt;SetTrack<span style="color:#d86ac2">(</span>vecSuspendedBars<span style="color:#008080">&#091;</span>i<span style="color:#008080">&#093;</span>, <span style="color:#6f008a">FALSE</span><span style="color:#d86ac2">)</span>;                <span style="color:#ffd702">}</span>            <span style="color:#1a94ff">}</span></pre><br></div><div>As I noted before the code related to suspending and resuming tracking I made to keep the popup displayed when a skin was applied was to add TPM_RECUSE to the flags passed in. I did not determine why a skin being applied caused the dismissal and no skin applied kept the popup from being dismissed when tracking the context menu on an item in that popup. The above code now keeps the popup from being dismissed while allowing correct tracking on the item I am showing the context menu for.</div>]]>
   </description>
   <pubDate>Tue, 01 Sep 2026 13:18:38 +0000</pubDate>
   <guid isPermaLink="true">http://forum.codejock.com/forum_posts.asp?TID=24694&amp;PID=79472&amp;title=context-menu-tracking-when-skinning#79472</guid>
  </item> 
  <item>
   <title><![CDATA[Toolkit Pro : Visual Studio 2026]]></title>
   <link>http://forum.codejock.com/forum_posts.asp?TID=24636&amp;PID=79471&amp;title=visual-studio-2026#79471</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="http://forum.codejock.com/member_profile.asp?PF=1263">Fredrik</a><br /><strong>Subject:</strong> Visual Studio 2026<br /><strong>Posted:</strong> 31 August 2026 at 7:23am<br /><br /><table width="99%"><tr><td class="BBquote"><img src="forum_images/quote_box.png" title="Originally posted by astoyan" alt="Originally posted by astoyan" style="vertical-align: text-bottom;" /> <strong>astoyan wrote:</strong><br /><br /><div>Hello,</div><div><br></div><div>Visual Studio 2026 support with the latest C++ standard option have been added to a new Toolkit Pro v26 major update that is about to be released.</div><div><br></div><div>Regards,</div><div>&nbsp; &nbsp;Alexander</div></td></tr></table><br><br>Hi! Any updated when the new version will be released? We'd like to update to VS 2026 as well.]]>
   </description>
   <pubDate>Mon, 31 Aug 2026 07:23:03 +0000</pubDate>
   <guid isPermaLink="true">http://forum.codejock.com/forum_posts.asp?TID=24636&amp;PID=79471&amp;title=visual-studio-2026#79471</guid>
  </item> 
  <item>
   <title><![CDATA[Toolkit Pro : CHTMLToolTip design issue.]]></title>
   <link>http://forum.codejock.com/forum_posts.asp?TID=24693&amp;PID=79470&amp;title=chtmltooltip-design-issue#79470</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="http://forum.codejock.com/member_profile.asp?PF=3213">rdhd</a><br /><strong>Subject:</strong> CHTMLToolTip design issue.<br /><strong>Posted:</strong> 14 August 2026 at 10:19am<br /><br /><div>I have long had to work around issues when using HTML tooltips due to how the tooltip context destroys and deletes the actual tooltip. The issue is with HTML tooltips which must pump messages while waiting on navigation. The problem is while navigation is occurring, the "safe" delete code can be called.</div><div><br></div><div>Our HTML tooltips are more dynamic and can take a bit longer for navigation to complete and I have had to resort to all sorts of gymnastics to avoid touching deleted memory when returning from the message pumping loop.&nbsp;</div><div><br></div><div><br></div><div>&nbsp;Yes, Codejock's own CHTMLToolTip has exactly the same vulnerability — and it has NO protection at all.<br><br>&nbsp; The scenario:<br><br>&nbsp; 1. FilterToolTipMessageHelper or SetStyle/ShowImage/ModifyToolTipStyle calls SAFE_DELETEWINDOW(m_pToolTip) — which is<br>&nbsp; just ptr-&gt;DestroyWindow(); delete ptr; ptr = NULL;<br>&nbsp; 2. CHTMLToolTip::GetToolSize (line 1785) has a PumpMessage loop at lines 1847-1855 waiting for the IE WebBrowser to<br>&nbsp; reach READYSTATE_COMPLETE. While pumping, a dispatched WM_MOUSEMOVE can flow through PreTranslateMessage →<br>&nbsp; FilterToolTipMessage → FilterToolTipMessageHelper, which can call SAFE_DELETEWINDOW(m_pToolTip) at line 2437.<br>&nbsp; 3. When that happens: DestroyWindow() runs (the real CWnd::DestroyWindow — no override), delete runs the destructor<br>&nbsp; (~CHTMLToolTip releases m_pBrowserApp, then ~CXTPToolTipContextToolTip and ~CWnd run), and then memory is freed.<br>&nbsp; Control returns to the PumpMessage loop inside GetToolSize, which is now executing on a freed this pointer.<br>&nbsp; 4. The next line — m_pBrowserApp-&gt;get_ReadyState(&amp;rs) at line 1854 — dereferences a freed IWebBrowser2* pointer<br>&nbsp; through a freed this.<br><br>&nbsp; Codejock has zero protection against this. No deferred DestroyWindow, no deferred delete, no m_bPumping flag, no<br>&nbsp; refcounting. The CHTMLToolTip class is shipped with a latent use-after-free.<br><br>&nbsp; The reason it rarely crashes in practice: Codejock's CHTMLToolTip is rarely used (most apps use xtpToolTipStandard or<br>&nbsp; xtpToolTipOffice), and when it is used, the IE READYSTATE_COMPLETE pump is usually very fast since the content is a<br>&nbsp; simple about: URL with inline HTML. The window of vulnerability is tiny — but it's there.<br><br>&nbsp; Your JHTMLToolTip greatly expanded the pump duration (navigating to file-based HTML, waiting for complex rendering,<br>&nbsp; doing multi-pass sizing), which is why you needed the three-layer defense. You weren't fixing a problem you introduced<br>&nbsp; — you were protecting against a bug Codejock shipped.</div><div><br></div><div><br></div><div>This begs the question - why isn't the CJ source using addref/release mechanism as all the tips are CWnd derived objects? I have code to call InternalAddRef and InternalRelease before and after the pumping code needed to use HTML tips but this "safe" delete, which isn't so safe for me makes no use of ref counting.</div><div><br></div><div>My workaround is complex and involves overriding new/delete operators, deferring the actual delete to later. Testing constantly to see if CJ called delete ... all sorts of stuff. But it still suffers from the fact the c++ destructor is called when CJ calls "delete ptr;" My hacks solved most of the crashes when I first used HTML tips but it isn't foolproof due to the destructor running.</div>]]>
   </description>
   <pubDate>Fri, 14 Aug 2026 10:19:01 +0000</pubDate>
   <guid isPermaLink="true">http://forum.codejock.com/forum_posts.asp?TID=24693&amp;PID=79470&amp;title=chtmltooltip-design-issue#79470</guid>
  </item> 
  <item>
   <title><![CDATA[Toolkit Pro : Wrong Polish translations in ToolkitPro]]></title>
   <link>http://forum.codejock.com/forum_posts.asp?TID=24691&amp;PID=79469&amp;title=wrong-polish-translations-in-toolkitpro#79469</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="http://forum.codejock.com/member_profile.asp?PF=8199">astoyan</a><br /><strong>Subject:</strong> Wrong Polish translations in ToolkitPro<br /><strong>Posted:</strong> 03 August 2026 at 10:45am<br /><br /><div>I'd like to confirm that all translations for all languages have been reviewed and corrected in the upcoming version. Once the update is available, please review it all again and report any new issues that you might notice.</div><div><br></div><div>Thank you.</div><div>Regards,</div><div>&nbsp; &nbsp;Alexander</div>]]>
   </description>
   <pubDate>Mon, 03 Aug 2026 10:45:10 +0000</pubDate>
   <guid isPermaLink="true">http://forum.codejock.com/forum_posts.asp?TID=24691&amp;PID=79469&amp;title=wrong-polish-translations-in-toolkitpro#79469</guid>
  </item> 
  <item>
   <title><![CDATA[Command Bars : customize dialog]]></title>
   <link>http://forum.codejock.com/forum_posts.asp?TID=24692&amp;PID=79467&amp;title=customize-dialog#79467</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="http://forum.codejock.com/member_profile.asp?PF=9646">coder89</a><br /><strong>Subject:</strong> customize dialog<br /><strong>Posted:</strong> 29 July 2026 at 11:36am<br /><br /><div>Hello,</div><div>I'm wondering how I can change the Caption of the Customize dialog? (e.g. "General Options")</div><div>Since I'm using only once custom page is possible to Hide the Tab General, just show the content.</div><div>How I can set the width and height of the dialog window? when creates the dialog is too small for the content and user has always to enlarge the window.</div><img src="uploads/9646/command_Customize.png" height="255" width="315" border="0" /><div><br></div><div>Many thanks in advanced.</div><div><br></div><div>Cheers<br><div><br></div></div>]]>
   </description>
   <pubDate>Wed, 29 Jul 2026 11:36:13 +0000</pubDate>
   <guid isPermaLink="true">http://forum.codejock.com/forum_posts.asp?TID=24692&amp;PID=79467&amp;title=customize-dialog#79467</guid>
  </item> 
  <item>
   <title><![CDATA[Toolkit Pro : Wrong Polish translations in ToolkitPro]]></title>
   <link>http://forum.codejock.com/forum_posts.asp?TID=24691&amp;PID=79466&amp;title=wrong-polish-translations-in-toolkitpro#79466</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="http://forum.codejock.com/member_profile.asp?PF=9273">jw_statica</a><br /><strong>Subject:</strong> Wrong Polish translations in ToolkitPro<br /><strong>Posted:</strong> 28 July 2026 at 4:18am<br /><br />A lot of localized resource files in Codejock have numerous translation errors.<div><br><div>For example, buttons that are meant to "Close" sometimes are translated as "Blisko" (near) rather than "Zamknij". "Save" is translated as "Ratować" (rescue) instead of "Zapisz". "Hex" as in hexadecimal was translated as "Klatwa" (curse). "Cut" was translated as "Skaleczenie" (wound) instead of "Wytnij", similarily "Paste" was simply translated to "Pasta" (food).&nbsp;</div><div><br></div><div>In general the translations have inconsistent grammatical forms, which along with bad translations may confuse our users whenever they use Codejock functionalities in our software primarily aimed at Polish customers.</div></div>]]>
   </description>
   <pubDate>Tue, 28 Jul 2026 04:18:14 +0000</pubDate>
   <guid isPermaLink="true">http://forum.codejock.com/forum_posts.asp?TID=24691&amp;PID=79466&amp;title=wrong-polish-translations-in-toolkitpro#79466</guid>
  </item> 
  <item>
   <title><![CDATA[Controls : Issues with Focus Management and Read-Only Error i]]></title>
   <link>http://forum.codejock.com/forum_posts.asp?TID=24648&amp;PID=79423&amp;title=issues-with-focus-management-and-readonly-error-i#79423</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="http://forum.codejock.com/member_profile.asp?PF=9673">eb_343</a><br /><strong>Subject:</strong> Issues with Focus Management and Read-Only Error i<br /><strong>Posted:</strong> 20 July 2026 at 8:11am<br /><br />Hello,<br><br>I am currently implementing the Codejock.FlatEdit.20.3.0 control within a Microsoft Access 2010 environment. My intention is to utilize it as a standard text input/editing field, similar to the native Access TextBox. However, I am facing two critical technical challenges:<br><br>&nbsp; &nbsp;1. Initialization Error: Upon loading the form, a runtime error occurs stating: “Property is read-only.”<br>&nbsp; &nbsp;2. Focus Issues: Once an edit operation is completed within the control, I am unable to shift the focus away from the FlatEdit control to other controls on the form or even to the form itself. It appears the control maintains a lock on the focus.<br><br>Could you please provide some guidance or best practices to resolve these behaviors?<br><br>Best regards,"]]>
   </description>
   <pubDate>Mon, 20 Jul 2026 08:11:18 +0000</pubDate>
   <guid isPermaLink="true">http://forum.codejock.com/forum_posts.asp?TID=24648&amp;PID=79423&amp;title=issues-with-focus-management-and-readonly-error-i#79423</guid>
  </item> 
 </channel>
</rss>