rnhmjoj/qutebrowser
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Merge branch 'lahwaacz-settings'

Browse Source
This commit is contained in:
Florian Bruhin 2016-08-29 07:09:29 +02:00
commit 074a5f86a2
2 changed files with 30 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
qutebrowser/html/settings.html
View File

@ -28,7 +28,7 @@ th pre { color: grey; text-align: left; }
<tr>
<td>{{ d }} (Current: {{ confget(section, d)|truncate(100) }})</td>
<td>
<input type="input"
<input type="text"
onblur="cset('{{ section }}', '{{ d }}', this)"
value="{{ confget(section, d) }}">
</input>

29
tests/end2end/features/set.feature
View File

@ -63,6 +63,35 @@ Feature: Setting settings.
Then the following tabs should be open:
- qute:settings (active)
@qtwebengine_todo: qute:settings is not implemented yet
Scenario: Focusing input fields in qute://settings and entering valid value
When I set general -> ignore-case to false
And I open qute://settings
# scroll to the right - the table does not fit in the default screen
And I run :scroll-perc -x 100
And I hint with args "inputs" and follow a
And I wait for "Entering mode KeyMode.insert *" in the log
And I press the key "<Ctrl+Backspace>"
And I press the keys "true"
And I press the key "<Escape>"
# an explicit Tab to unfocus the input field seems to stabilize the tests
And I press the key "<Tab>"
Then general -> ignore-case should be true
@qtwebengine_todo: qute:settings is not implemented yet
Scenario: Focusing input fields in qute://settings and entering invalid value
When I open qute://settings
# scroll to the right - the table does not fit in the default screen
And I run :scroll-perc -x 100
And I hint with args "inputs" and follow a
And I wait for "Entering mode KeyMode.insert *" in the log
And I press the key "<Ctrl+Backspace>"
And I press the keys "foo"
And I press the key "<Escape>"
# an explicit Tab to unfocus the input field seems to stabilize the tests
And I press the key "<Tab>"
Then "Invalid value 'foo' *" should be logged
Scenario: Empty option with ? (issue 1109)
When I run :set general ?
Then the error "set: The following arguments are required: value" should be shown