Feature request: anchor tags on ChangeLog web page

[Buckit]

Hey guys,

 

Just a tiny suggestion: would it be possible for you to update the PasswordState Change Log webpage to include anchor tags in each update's header? For example, if I'd like to specifically link to build 8180, it'd be great to have something like https://www.clickstudios.com.au/passwordstate-changelog.aspx#8180. The changelog has grown to considerable size, so it'd help my colleagues if they didn't have to <ctr><f> for a buildnum.

 

It could be as simple as changing this:

<h3>
  Passwordstate 8.1 - Build 8180 (21st November 2017)&nbsp;
  <img src="/images/dbschemaupdates.png" alt="Database Schema Updates in this Build" style="padding-bottom: 3px;">
</h3>

 

...to this:

<h3>
  <a name="8180">Passwordstate 8.1 - Build 8180 (21st November 2017)</a>&nbsp;
  <img src="/images/dbschemaupdates.png" alt="Database Schema Updates in this Build" style="padding-bottom: 3px;">
</h3>

 

Take care! :)

[support]

Hey Buckit,

 

We we take a look and see if this will be a simple change.  If it is we'll include it in a future build.

 

Regards,

Support

 

[Buckit]

I appreciate it

 

It's of course well and good for me to say "it should be as simple as ...", but that's a stupid remark of course. I have no way of knowing your code. The end-result may be simple (an added HTML tag), but there's no telling how the page gets generated. Something-something-assumptions.

[support]

Hi Buckit,

 

I had a quick look at this request today, and I think our web site theme causes issues with these - see how the heading/text is hidden under the top blue header? This would mean you need to scroll up to see it

 

[Buckit]

It took me a while to process what you were saying, now I understand it... Yeah, this seems to be an issue with overlapping DIVs, so it'd require some tweaks in another location (probably lowering the Y-axis of the main DIV by the height of the top bar). I really appreciate you looking into this so quickly though :)

[Sarge]

I messed around with the object inspector for about 30 minutes but gave up, however position:sticky seemed like it would have got me there if my CSS-foo was better.

Although to be honest, I think each build should have its own release notes page containing the usual, whats new, whats fixed, whats changed, known bugs, then do away with the "change log" and turn it into a "release log" TOC linking to the builds release notes and their downloads (https://www.clickstudios.com.au/previous-builds.aspx).

 

[support]

Thanks Sarge.