most recent 30 from http://fogbugz.stackexchange.com 2013-05-22T13:42:13Z http://fogbugz.stackexchange.com/feeds/question/47 http://www.creativecommons.org/licenses/by-nc/2.5/rdf http://fogbugz.stackexchange.com/questions/47/feature-request-anchors-for-bugmonkey-customization Roman 2009-09-14T19:38:56Z 2012-09-25T13:10:21Z

<p>When writing Bugmonkey scripts it's hard to parse the html to find just the right element you want to modify.</p> <p>Let's say that you have a custom field which is meant to store id numbers of customers in your CRM tool. In order to convert these to links with bugmonkey you need to parse the html to find the correct element in order to replace those ids with urls. The result seems to be hit and miss depending on how the page was rendered.</p> <p>If, however, the custom field had an id attribute which could be used as an anchor (for example to be able to find directly on the page with getElementByID) it would make writing these scripts a lot easier.</p> <p>Although in this case I'm talking about custom fields, I'm sure there are other places where this could be useful.</p> <blockquote> <p><img src="http://www.gravatar.com/avatar/baf927dcc0b0c5d0f41dece1e575aa0f?s=32&amp;d=identicon&amp;r=PG" alt="Fog Creek"> <a href="http://fogbugz.stackexchange.com/questions/1023/whats-that-kiwi-logo-and-case-number-at-the-bottom-of-my-feature-request" rel="nofollow">Case FC2038241</a></p> </blockquote>

http://fogbugz.stackexchange.com/questions/47/feature-request-anchors-for-bugmonkey-customization/51#51 Michael Pryor 2009-09-15T05:03:12Z 2009-09-15T05:03:12Z

<p>It's a good suggestion, but it's also an interface that we have to adhere to. i.e. it's essentially an API. I'm not saying we shouldn't do this, just pointing out that it's not as simple as throwing a bunch of ids all over the place, as it needs to be documented and supported into the future as soon as we do it...</p>