[savannah-help-public] [sr #109693] Full Markup and Rich Markup help links replace editing page

[Ineiev]

URL:
  

 Summary: Full Markup and Rich Markup help links replace
editing page
 Project: Savannah Administration
Submitted by: peterdd
Submitted on: Thu 06 Jun 2019 08:16:46 AM UTC
 Should Start On: Wed 05 Jun 2019 10:00:00 PM UTC
   Should be Finished on: Wed 05 Jun 2019 10:00:00 PM UTC
Category: None
Priority: 3 - Low
  Status: None
 Privacy: Public
Percent Complete: 0%
 Assigned to: None
 Open/Closed: Open
 Discussion Lock: Any
  Effort: 0.00

___

Details:

That is annoying when you type a task or comment and just want to view the
flavor of savannah markdown rules and bam! - page replaced.

A simple fix for that is a target="_blank" attribute of that links.

More fancy tooltips without opening a new tab/window are possible with pure
css too, but require change of markup too(1 input checkbox tag, 2 label tags,
1 div tag containing the markdown help info, and several css rules)




___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/

[savannah-help-public] [sr #109694] replace SV_THEME cookie with db stored user preference

[Ineiev]

URL:
  

 Summary: replace SV_THEME cookie with db stored user
preference
 Project: Savannah Administration
Submitted by: peterdd
Submitted on: Thu 06 Jun 2019 08:17:30 AM UTC
 Should Start On: Wed 05 Jun 2019 10:00:00 PM UTC
   Should be Finished on: Wed 05 Jun 2019 10:00:00 PM UTC
Category: None
Priority: 3 - Low
  Status: None
 Privacy: Public
Percent Complete: 0%
 Assigned to: None
 Open/Closed: Open
 Discussion Lock: Any
  Effort: 0.00

___

Details:

My web browser is intentional configured to delete all cookies when closed.

This makes setting a theme cookie in savannah quite useless for such dudes
like me.

Also savannah.nongnu.org and savannah.gnu.org store each their own SV_THEME
cookie, so setting the theme on one site does not apply to the other site.

A solution to this would be storing the theme setting in a database field of
the user.

Also while watching the cookies in web develeoper tools I saw the SV_THEME
cookie was sometimes stored with different Domain range: 

Name Domain
SV_THEME .savannah.nongnu.org
SV_THEME savannah.nongnu.org





___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/

[savannah-help-public] [sr #109695] remove text-shadow from h1.prioxxxxx of base.css

[Ineiev]

URL:
  

 Summary: remove text-shadow from h1.priox of base.css
 Project: Savannah Administration
Submitted by: peterdd
Submitted on: Thu 06 Jun 2019 08:17:51 AM UTC
 Should Start On: Wed 05 Jun 2019 10:00:00 PM UTC
   Should be Finished on: Wed 05 Jun 2019 10:00:00 PM UTC
Category: None
Priority: 5 - Normal
  Status: None
 Privacy: Public
Percent Complete: 0%
 Assigned to: None
 Open/Closed: Open
 Discussion Lock: Any
  Effort: 0.00

___

Details:

The title with a text-shadow is harder to read and looks even more weired when
combined with other color themes than the default theme.

If a theme wants to style h1 heading in a weired way, they can do that in
their theme, but the text-shadow and color should not be in the base.css .
IMHO.




___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/

[savannah-help-public] [sr #109693] Full Markup and Rich Markup help links replace editing page

[Ineiev]

Update of sr #109693 (project administration):

  Status:None => Works For Me   
 Assigned to:None => ineiev 

___

Follow-up Comment #2:

This request doesn't seem valid for me.

If you want to the reminder in the same place, visit the link, and then you
can return to "previous" page; if you want it in new window or tab, act
accordingly; modifying the default link behavior is going to produce more
surprise.

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/

[savannah-help-public] [sr #109694] replace SV_THEME cookie with db stored user preference

[Ineiev]

Update of sr #109694 (project administration):

Category:None => Savannah website   
  Status:None => In Progress
 Assigned to:None => ineiev 


___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/

[savannah-help-public] [sr #109695] remove text-shadow from h1.prioxxxxx of base.css

[Ineiev]

Update of sr #109695 (project administration):

Category:None => Savannah website   
  Status:None => Done   
 Assigned to:None => ineiev 
 Open/Closed:Open => Closed 

___

Follow-up Comment #2:

Done.

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/

[savannah-help-public] [sr #109694] replace SV_THEME cookie with db stored user preference

[Ineiev]

Update of sr #109694 (project administration):

  Status: In Progress => Need Info  

___

Follow-up Comment #2:

SV_THEME _is_ stored in user preferences; in fact, you can only handle it
(with Savannah UI) when logged-in.

Yes, having Siamese twin websites *.gnu.* and *.nongnu.* results in
inconsistencies, but I don't think this is important.

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/

[savannah-help-public] [sr #109693] Full Markup and Rich Markup help links replace editing page

[Peter Liscovius]

Follow-up Comment #3, sr #109693 (project administration):

Ok, let me explain my position deeper:

Imaging a user writes an item (bug, task, support, comment,..), took time to
formulate the problem, proof read and finally wants to add some markdown sugar
for formatting stuff. The helper link 'Rich Markup' is positioned very near
the input text area. What a user would expect?

I am sure most users are frightened to death seeing that all their work seems
immediatly lost and never will try to use again the markdown helper link for
fear loosing their work in future. Or even never participate again in projects
hosted by a savane / savannah.gnu.org due such bad experience.

In a try to revert a user _could_ use the *back button* of their browser, but
I know systems where that does not work. I also think that it is just a
convenience of todays web browsers to remember the input made on the previous
page. (have not verified it)

The quick fix target="_blank" was just a simple example how to avoid that.
BTW, I am not the only one that sees a problem with opening a help link
replacing same window:

https://www.standardaccesskeys.com/SAK2014/#spec


Access Key   ScopeLocation   Window/Tab
0 (zero) Page Help   New Window



But as I wrote, there are also softer CSS solutions to that problem that are
not such brutal as like opening a separate tab/new window:

Here is an example of how to implement a *CSS only* html tooltip that just
overlays, not loads another page.
I implemented that css only solution on bugs.flyspray.org for keyboard
shortcuts.

I use *s_* as id-prefix for storing a 'status' in a input checkbox and the
different labels toggle that status. The label tags MUST direct follow the
input tag  in code, but can appear everywhere visual on the page due CSS.

The HTML:


icon Rich Markup


close icon
The mdhelp content html



The CSS:

#mdhelplabel {cursor:pointer;padding-left:1em;}
#mdhelpclose {cursor:pointer;float:right; }
#mdhelp {
  display:none;
  position:fixed;
  z-index:100;
  background:#fff;
  border:1px solid #999;
  border-radius:10px;
  padding:10px;
  box-shadow:0 0 400px #000;
  top:50%;
  margin-top:-250px;
  height:520px;
  left:50%;
  width:300px;
  margin-left:-150px;
  box-sizing:border-box;
}
#mdhelpmodal {
  background-color: rgba(0, 0, 0, 0.3);
  display: none;
  height: 100%;
  left: 0;
  position: fixed;
  top: 0;
  width: 100%;
  z-index: 99;
  cursor:pointer;
}
#s_mdhelp {display:none;}
#s_mdhelp:checked ~ #mdhelp, #s_mdhelp:checked ~ #mdhelpmodal {display:
block;}


___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/

[savannah-help-public] [sr #109696] markdown verbatim (for code snippets) does not respect white-space

[Peter Liscovius]

URL:
  

 Summary: markdown verbatim (for code snippets) does not
respect white-space
 Project: Savannah Administration
Submitted by: peterdd
Submitted on: Thu 06 Jun 2019 08:16:28 PM CEST
Category: Savannah trackers - bugs, tasks, etc.
Priority: 5 - Normal
Severity: 3 - Normal
  Status: None
 Assigned to: None
Originator Email: 
Operating System: None
 Open/Closed: Open
 Discussion Lock: Any

___

Details:

spaces (single space, tabs, ..) are not preserved in output of savane markdown
_verbatim_ areas.

Easiest solution is to replace the p-tag within the blockquote-tag by a
pre-tag, that has CSS


display: block;
font-family: monospace;
white-space: pre;


by default in web browsers.

And then there is no need for putting extra br-tags there too.




___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/